| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Oleg Serov <serovov(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Diffrent column ordering after dump/restore tables with INHERITS |
| Date: | 2009-07-05 16:10:36 |
| Message-ID: | 407d949e0907050910l11493097j8a679c7a2bb78ae4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Jul 5, 2009 at 4:28 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-07-05 16:15:12 | Re: Diffrent column ordering after dump/restore tables with INHERITS |
| Previous Message | Tom Lane | 2009-07-05 15:55:05 | Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore |