Horton

Re: creating CHECK constraints as NOT VALID

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

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Jaime Casanova <jaime@2ndquadrant.com>, Dean Rasheed <dean.a.rasheed@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-15T23:32:29Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix pg_get_constraintdef to cope with NOT VALID constraints

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.

			regards, tom lane