| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Oleg Serov <serovov(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Diffrent column ordering after dump/restore tables with INHERITS |
| Date: | 2010-02-26 15:13:51 |
| Message-ID: | 407d949e1002260713t3f92600ejdccaed9d8a4426cd@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2010/2/26 Oleg Serov <serovov(at)gmail(dot)com>:
> Up! Anybody will answer about the patch?
The patch causes the inheritance history to be lost. If you
subsequently drop the column form the parent it'll be kept on the
child because it was explicitly declared when you created the child.
In the original structure if you dropped the column from the parent it
would be dropped from the child because it was an inherited column.
Inheritance is in a kind of no-mans land. It's not good enough to be
an important feature anyone cares enough about to make it work
properly and it's not shoddy enough that it's worth removing. I'm sure
there are people using it effectively despite the caveats and rough
edges.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-26 15:52:33 | Re: BUG #5347: initdb does not work when a data directory has been deleted |
| Previous Message | Oleg Serov | 2010-02-26 14:34:30 | Re: Diffrent column ordering after dump/restore tables with INHERITS |