Re: creating CHECK constraints as NOT VALID

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: creating CHECK constraints as NOT VALID
Date: 2011-06-16 00:08:09
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Excerpts from Tom Lane's message of mié jun 15 19:32:29 -0400 2011:
> Alvaro Herrera <alvherre(at)commandprompt(dot)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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment Content-Type Size
not-valid-check-5.patch application/octet-stream 49.5 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2011-06-16 00:52:12 Symbols and versioning of binary releases; running a symbol server
Previous Message Simon Riggs 2011-06-15 23:33:55 Re: Strict Set Returning Functions