Re: BUG #6024: pg_dump won't dump ALTERed inherited fields - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6024: pg_dump won't dump ALTERed inherited fields
Date
Msg-id 16597.1305213853@sss.pgh.pa.us
Whole thread Raw
In response to BUG #6024: pg_dump won't dump ALTERed inherited fields  ("Panos Christeas" <xrg@linux.gr>)
Responses Re: BUG #6024: pg_dump won't dump ALTERed inherited fields
Re: BUG #6024: pg_dump won't dump ALTERed inherited fields
List pgsql-bugs
"Panos Christeas" <xrg@linux.gr> writes:
> CREATE TABLE test1(
>     id SERIAL PRIMARY KEY,
>     name VARCHAR(20) NOT NULL
>     );

> CREATE TABLE test2(
>     description TEXT
>     ) INHERITS(test1);

> ALTER TABLE test2 ALTER name DROP NOT NULL;

> pg_dump that.
> The dump will still have "not null" constraint at test2.name.

This isn't really a pg_dump deficiency.  The bug is that we let you do
that ALTER.  Inherited constraints shouldn't be droppable, and indeed
are not droppable except in the single case of NOT NULL.  This is on the
to-fix list --- in fact there was a patch submitted for it last year,
although it got returned for rework and we've not seen it again yet.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: Adding a user without expiration date using pgAdmin III causes postgresql Beta1 to crash
Next
From: "P. Christeas"
Date:
Subject: Re: BUG #6024: pg_dump won't dump ALTERed inherited fields