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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oleg Serov <serovov(at)gmail(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Diffrent column ordering after dump/restore tables with INHERITS
Date: 2010-02-26 19:32:51
Message-ID: 20100226193251.GE3980@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane escribió:
> Oleg Serov <serovov(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Teodor Sigaev 2010-02-26 20:12:25 Re: [BUGS] BUG #5021: ts_parse doesn't recognize email addresses with underscores
Previous Message Tom Lane 2010-02-26 18:29:54 Re: Diffrent column ordering after dump/restore tables with INHERITS