<depst...@alliedtesting.com> writes:
> I noticed that when pg_dump saves SQL code for a table with inheritance, it
> does not save any information about inherited columns. This is fine when
> inherited columns do not undergo any modification, but when they do, that
> information is lost.
> Example:
> create table parent (id integer not null);
> create table child (value integer) inherits (parent);
> alter table child alter column id drop not null;
Actually, the bug here is that ALTER TABLE lets you do that. Dropping
an inherited constraint should be disallowed, and is disallowed for the
case of CHECK constraints. We haven't gotten around to enhancing the
NOT NULL infrastructure to detect that, but it's on the TODO list.
In the meantime, there's no point in modifying pg_dump to worry about
such cases.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
