[GH-ISSUE #6] Child tables are not dispayed #5

New issue

Closed

opened 2026-05-05 03:29:01 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 03:29:01 -06:00

Owner

Originally created by @glushakov on GitHub (May 6, 2020).
Original GitHub issue: https://github.com/levinsv/pgadmin3/issues/6

Hi. With inherit partititioning, child tables are not display in tree. In parent table (partitions sub menu) there are also not.
Checked on pg 10

Originally created by @glushakov on GitHub (May 6, 2020). Original GitHub issue: https://github.com/levinsv/pgadmin3/issues/6 Hi. With inherit partititioning, child tables are not display in tree. In parent table (partitions sub menu) there are also not. Checked on pg 10

gitea-mirror closed this issue

2026-05-05 03:29:06 -06:00

gitea-mirror commented

2026-05-05 03:29:11 -06:00

Author

Owner

@levinsv commented on GitHub (May 7, 2020):

Hi.
In my test case, everything is Ok.

CREATE TABLE cities (
    name            text,
    population      float,
    altitude        int     -- в футах
);

CREATE TABLE capitals (
    state           char(2)
) INHERITS (cities);

What are your SQL commands?

@levinsv commented on GitHub (May 7, 2020): Hi. In my test case, everything is Ok. ``` CREATE TABLE cities ( name text, population float, altitude int -- в футах ); CREATE TABLE capitals ( state char(2) ) INHERITS (cities); ``` What are your SQL commands?

gitea-mirror referenced this issue

2026-05-05 03:29:15 -06:00

[GH-ISSUE #5] Can't Open/Connect to Newly Created Postgres 10 database #4

gitea-mirror commented

2026-05-05 03:29:15 -06:00

Author

Owner

@glushakov commented on GitHub (May 8, 2020):

it looks like problem appear when child table placed in different schema then parent table.
My case:

CREATE TABLE public.history
(
itemid bigint NOT NULL,
clock integer NOT NULL DEFAULT 0,
value numeric(16,4) NOT NULL DEFAULT 0.0000,
ns integer NOT NULL DEFAULT 0
);

CREATE TABLE partitions.history_p2020_04_09
(

CONSTRAINT history_p2020_04_09_clock_check CHECK (clock >= 1586379600 AND clock < 1586466000)
)
INHERITS (public.history)
WITH (
OIDS=FALSE
);

@glushakov commented on GitHub (May 8, 2020): it looks like problem appear when child table placed in different schema then parent table. My case: CREATE TABLE public.history ( itemid bigint NOT NULL, clock integer NOT NULL DEFAULT 0, value numeric(16,4) NOT NULL DEFAULT 0.0000, ns integer NOT NULL DEFAULT 0 ); CREATE TABLE partitions.history_p2020_04_09 ( CONSTRAINT history_p2020_04_09_clock_check CHECK (clock >= 1586379600 AND clock < 1586466000) ) INHERITS (public.history) WITH ( OIDS=FALSE );

gitea-mirror commented

2026-05-05 03:29:18 -06:00

Author

Owner

@glushakov commented on GitHub (May 8, 2020):

with declarative partitioning the situation is similar

@glushakov commented on GitHub (May 8, 2020): with declarative partitioning the situation is similar