Skip site navigation (1) Skip section navigation (2)

Re: AW: Proposal: More flexible backup/restore via pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Stephan Szabo" <sszabo(at)kick(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: AW: Proposal: More flexible backup/restore via pg_dump
Date: 2000-06-30 00:30:58
Message-ID: 2475.962325058@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
"Stephan Szabo" <sszabo(at)kick(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2000-06-30 00:43:32
Subject: Re: Big 7.1 open items
Previous:From: Hiroshi InoueDate: 2000-06-29 23:59:49
Subject: Re: AW: Big 7.1 open items

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group