Re: AW: Proposal: More flexible backup/restore via pg_dump - Mailing list pgsql-hackers

From Tom Lane
Subject Re: AW: Proposal: More flexible backup/restore via pg_dump
Date
Msg-id 2475.962325058@sss.pgh.pa.us
Whole thread Raw
In response to Re: AW: Proposal: More flexible backup/restore via pg_dump  ("Stephan Szabo" <sszabo@kick.com>)
Responses Re: AW: Proposal: More flexible backup/restore via pg_dump  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
"Stephan Szabo" <sszabo@kick.com> writes:
>> If we had ALTER TABLE ADD CONSTRAINT then the problem would be largely
>> solved, I believe.  This should be a minor exercise --- the heavy
>> lifting is already done, because heap.c's AddRelationRawConstraints()
>> is already set up to be invokable on a pre-existing relation.

> Does the AddRelationRawConstraints() check that the constraint is
> satisified as well when you add it?  It didn't look like it did, but I
> could be missing something.

Oh, you're right, it does not.  So you'd first have to run through the
table and verify that the constraint holds for each existing tuple.
Doesn't seem like a big deal though...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: AW: Big 7.1 open items
Next
From: Tom Lane
Date:
Subject: Re: Big 7.1 open items