| From: | Oleg Serov <serovov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-27 14:13:54 |
| Message-ID: | cec7c6df1002270613r43bc17edxf0baf9f57d3757d6@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Feb 26, 2010 at 9:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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
>
It is a bug. If i'm doing dump restore i must have _same_ database structure
as i dumped. Yes?
> child column orders inconsistent. Would you prefer that we restricted
> ALTER TABLE to refuse to perform the alteration in the first place?
>
No! it is not right. We must think how to solve this problem correct.
> regards, tom lane
>
--
С уважением
Олег Серов
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raphael Palestino Serpa | 2010-02-27 14:15:19 | |
| Previous Message | Tom Lane | 2010-02-27 01:33:23 | Re: bug in string comparison |