>On Monday, 4 January 2016 8:24 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>Either way, however, the way you declared c2, it has an independent >local definition of all four columns, and so they should not go away >even if the parent's columns go away. This is exactly the purpose >that attislocal was created to serve, and your patch destroys it. Understood this is not a bug, thank you. I missed ALTER TABLE statement in previous test case, correct test case is as follow: -- create table CREATE TABLE p1 (a int , b int); CREATE TABLE c2 (a int , b int); -- alter c2' inheritance ALTER TABLE c2 INHERIT p1; -- drop column b ALTER TABLE p1 DROP COLUMN b; -- table description postgres=# \d p1 Table "public.p1" Column | Type | Modifiers --------+---------+----------- a | integer | Number of child tables: 1 (Use \d+ to list them.) postgres=# \d c2 Table "public.c2" Column | Type | Modifiers --------+---------+----------- a | integer | b | integer | Inherits: p1 Regards, Amul Sul -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
