Horton

Re: creating CHECK constraints as NOT VALID

Alvaro Herrera <alvherre@commandprompt.com>

View thread
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Thom Brown <thom@linux.com>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-04T01:04:46Z
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

Excerpts from Thom Brown's message of vie jun 03 13:45:57 -0400 2011:
> On 3 June 2011 17:58, Alvaro Herrera <alvherre@commandprompt.com> wrote:
> > Excerpts from Thom Brown's message of vie jun 03 12:47:58 -0400 2011:

> >> Nice work Alvaro :)  Shouldn't patches be sent to -hackers instead of
> >> the obsolete -patches list?  Plus I'm a bit confused as to why the
> >> patch looks like an email instead of a patch.
> >
> > Did I really email pgsql-patches?  If so, I didn't notice -- but I don't
> > see it (and the archives seem to agree with me, there's no email after
> > 2008-10).
> 
> My bad, I was reading your patch which contained an email subject
> beginning with [PATCH] (similar to mailing list subject prefixes)
> which, if I had given it any further though, doesn't mean it's on the
> -patches list.

Ah, that makes sense.  The pgsql-patches tag was [PATCHES] actually,
though :-)

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