Re: Teaching pg_dump to use NOT VALID constraints - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Teaching pg_dump to use NOT VALID constraints
Date
Msg-id 54654D25.7010100@gmx.net
Whole thread Raw
In response to Re: Teaching pg_dump to use NOT VALID constraints  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Teaching pg_dump to use NOT VALID constraints  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 11/13/14 5:07 AM, Simon Riggs wrote:
> On 13 November 2014 00:20, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> 
>> Isn't the real use-case here that if constraints were valid when you dumped
>> then we shouldn't have to *any* re-validate when we load? (Though, we'd have
>> to be careful of that with CHECK because that can call user code...)
> 
> Yes, that is the use case this patch would improve considerably.

But your patch doesn't really address that.  It just leaves the
constraints as invalid, and someone will have to revalidate them later
(how?).  What Jim was describing was a mode that creates the constraints
as valid but doesn't actually validate them.  I can see both sides of
that kind of feature.




pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: using custom scan nodes to prototype parallel sequential scan
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Performance issue with libpq prepared queries on 9.3 and 9.4