Re: creating CHECK constraints as NOT VALID

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

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-15T16:53:59Z

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 →

Fix pg_get_constraintdef to cope with NOT VALID constraints
- 048417511aef 9.1.0 cited

On Wed, Jun 15, 2011 at 12:24 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Hmm, I think this means we need to send a sinval message to invalidate
> cached plans when a constraint is validated.  I'll see about this.

I feel like that really ought to be happening automatically, as a
result of committing the transaction that did the system catalog
modification.  It seems pretty strange if it isn't.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company