Re: Teaching pg_dump to use NOT VALID constraints

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Teaching pg_dump to use NOT VALID constraints
Date: 2014-11-13 10:07:24
Message-ID: CA+U5nMJqCScq0VyHt0dPGe8rxO7jkFMDSoF3qEK9EJ_L+L2xug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 13 November 2014 00:20, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2014-11-13 10:45:56 Typos in CREATE TABLE doc
Previous Message Jeff Davis 2014-11-13 08:38:55 Re: group locking: incomplete patch, just for discussion