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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Serov <serovov(at)gmail(dot)com>
Cc: 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 18:29:54
Message-ID: 1468.1267208994@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2010-02-26 19:32:51 Re: Diffrent column ordering after dump/restore tables with INHERITS
Previous Message Oleg Serov 2010-02-26 18:22:27 Re: Diffrent column ordering after dump/restore tables with INHERITS