Re: creating CHECK constraints as NOT VALID

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Jaime Casanova <jaime@2ndquadrant.com>, Dean Rasheed <dean.a.rasheed@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2011-06-16T00:08:09Z

Lists: pgsql-hackers

Attachments

not-valid-check-5.patch (application/octet-stream)

Excerpts from Tom Lane's message of mié jun 15 19:32:29 -0400 2011:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Here's an updated patch fixing all of the above.  I stole your first
> > test case and added it to regression, after some editorialization.
> 
> I've probably created some merge conflicts for you in process of fixing
> the FOREIGN KEY NOT VALID patch, but in any case you need to change this
> to use ConstraintAttributeSpec rather than a duplicate production.

Yeah, nothing serious.  Updated patch attached.  The wording in the doc
changes could probably use some look over.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support