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

From Simon Riggs
Subject Re: Teaching pg_dump to use NOT VALID constraints
Date
Msg-id CA+U5nMJqCScq0VyHt0dPGe8rxO7jkFMDSoF3qEK9EJ_L+L2xug@mail.gmail.com
Whole thread Raw
In response to Re: Teaching pg_dump to use NOT VALID constraints  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Teaching pg_dump to use NOT VALID constraints  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
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.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: group locking: incomplete patch, just for discussion
Next
From: Etsuro Fujita
Date:
Subject: Typos in CREATE TABLE doc