Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: majid(at)apsalar(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns
Date: 2014-03-13 14:19:00
Message-ID: 15349.1394720340@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> majid(at)apsalar(dot)com wrote:
>> Reproduction case:
>>
>> create table A(a int, b int, c int);
>> create table B(a int, c int);
>> alter table A inherit B;

> I wonder if the real fix here is to have ALTER / INHERIT error out of
> the columns in B are not a prefix of those in A.

Years ago, we sweated quite a lot of blood to make these cases work.
I'm not thrilled about throwing away all that effort because one person
doesn't like the behavior.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Yong Zhang 2014-03-13 14:28:47 Re: BUG #9531: Failed to install
Previous Message Tom Lane 2014-03-13 14:05:05 Re: BUG #9553: why bitmap index scan startup_cost=0? it's a bug?

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-03-13 14:20:56 Re: [PATCH] Store Extension Options
Previous Message Tom Lane 2014-03-13 14:17:17 Re: Patch: show relation and tuple infos of a lock to acquire