Re: creating CHECK constraints as NOT VALID - Mailing list pgsql-hackers

From Robert Haas
Subject Re: creating CHECK constraints as NOT VALID
Date
Msg-id BANLkTi=rPJ+o+HWNiayfbgu5Y+WssOejdg@mail.gmail.com
Whole thread Raw
In response to Re: creating CHECK constraints as NOT VALID  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: creating CHECK constraints as NOT VALID
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: procpid?
Next
From: Simon Riggs
Date:
Subject: Strict Set Returning Functions