Re: Diffrent column ordering after dump/restore tables with INHERITS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Oleg Serov <serovov(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS
Date: 2009-07-05 16:18:39
Message-ID: 10070.1246810719@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Greg Stark <gsstark(at)mit(dot)edu> writes:
> On Sun, Jul 5, 2009 at 4:28 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This is not a bug, it's the intended behavior.

> I thought that was a bug, just one that was too hard to fix for the
> problems it caused. It might be more fixable if we get around to the
> work that was discussed earlier where we separate attnum into three
> different values.

Well, if you want to say there's a bug here, it's that ALTER TABLE ADD
COLUMN doesn't put the column in the "right" place to start with.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Steve Purcell 2009-07-05 16:37:35 Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore
Previous Message Greg Stark 2009-07-05 16:15:12 Re: Diffrent column ordering after dump/restore tables with INHERITS