Re: pg_dump: use ALTER TABLE for PKs - Mailing list pgsql-hackers

From Stephan Szabo
Subject Re: pg_dump: use ALTER TABLE for PKs
Date
Msg-id 20020219130125.D89690-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Re: pg_dump: use ALTER TABLE for PKs  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: pg_dump: use ALTER TABLE for PKs  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
On Wed, 20 Feb 2002, Philip Warner wrote:

> At 21:26 18/02/02 -0500, Neil Conway wrote:
> >
> >Bruce suggested that this should get some code review, since a bug in
> >pg_dump would be bad news. Any comments would be welcome.
> >
>
> Part of the reason I did not implement this earlier was that ALTER
> TABLE...PK did not handle child tables 'properly' (for some arbitrary
> meaning of the word 'properly'). How have you covered:
>
>     CREATE TABLE PARENT(F1 INT PRIMARY KEY);
>     CREATE TABLE CHILD(...) INHERIT PARENT
>
> this should create a PK on CHILD; what does pg-dump and the ALTER TABLE
> implementation do? Not sure how it should work, but ultimately we need to

Unless it was changed between rc2 and release, the above type of
sequence does not end up with a primary key on child(f1).




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Information about XLogWrite
Next
From: Philip Warner
Date:
Subject: Re: pg_dump: use ALTER TABLE for PKs