Re: creating CHECK constraints as NOT VALID

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
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-15 16:53:59
Message-ID: BANLkTi=rPJ+o+HWNiayfbgu5Y+WssOejdg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 15, 2011 at 12:24 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-06-15 17:03:59 Strict Set Returning Functions
Previous Message Bernd Helmle 2011-06-15 16:53:24 Re: procpid?