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

I'm think you should add some abstract-layer for handling column ordering
not as they stored at disk. It is possible?

On Fri, Feb 26, 2010 at 10:32 PM, Alvaro Herrera <alvherre@commandprompt.com
> wrote:

> Tom Lane escribi=C3=B3:
> > Oleg Serov <serovov@gmail.com> writes:
> > > So there are no simple way to do it right, and it will be not fixed?
> Will
> > > this bug appear in todo list?
> >
> > It's not a bug, it's just what happens when you make the parent and
> > child column orders inconsistent.  Would you prefer that we restricted
> > ALTER TABLE to refuse to perform the alteration in the first place?
>
> Possibly the right fix is to implement the oft-discussed idea about
> columns able to be moved around in table definitions.  That would let
> ALTER TABLE ADD COLUMN to put the column in the right positions in
> children.
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>



--=20
=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC

=D0=9E=D0=BB=D0=B5=D0=B3 =D0=A1=D0=B5=D1=80=D0=BE=D0=B2