Re: Diffrent column ordering after dump/restore tables with INHERITS - Mailing list pgsql-bugs

From Greg Stark
Subject Re: Diffrent column ordering after dump/restore tables with INHERITS
Date
Msg-id 407d949e0907050910l11493097j8a679c7a2bb78ae4@mail.gmail.com
Whole thread Raw
In response to Re: Diffrent column ordering after dump/restore tables with INHERITS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Diffrent column ordering after dump/restore tables with INHERITS  (Greg Stark <gsstark@mit.edu>)
Re: Diffrent column ordering after dump/restore tables with INHERITS  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Diffrent column ordering after dump/restore tables with INHERITS  (Oleg Serov <serovov@gmail.com>)
List pgsql-bugs
On Sun, Jul 5, 2009 at 4:28 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> when i done dump->restore i
>> have surprise,
>> Column ordering was changed.
>
> 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.

Oleg: note that having the columns in the same position allows some
optimizations in the executor so it's probably a good thing if it
hasn't broken your application.

--
greg
http://mit.edu/~gsstark/resume.pdf

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore
Next
From: Greg Stark
Date:
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS