Re: Diffrent column ordering after dump/restore tables with INHERITS - Mailing list pgsql-bugs

From Greg Stark
Subject Re: Diffrent column ordering after dump/restore tables with INHERITS
Date
Msg-id 407d949e1002260713t3f92600ejdccaed9d8a4426cd@mail.gmail.com
Whole thread Raw
In response to Re: Diffrent column ordering after dump/restore tables with INHERITS  (Oleg Serov <serovov@gmail.com>)
Responses Re: Diffrent column ordering after dump/restore tables with INHERITS  (Oleg Serov <serovov@gmail.com>)
List pgsql-bugs
2010/2/26 Oleg Serov <serovov@gmail.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

pgsql-bugs by date:

Previous
From: "David Andersen"
Date:
Subject: BUG #5347: initdb does not work when a data directory has been deleted
Next
From: Tom Lane
Date:
Subject: Re: BUG #5347: initdb does not work when a data directory has been deleted