| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(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 17:06:40 |
| Message-ID: | 1308157510-sup-5997@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Robert Haas's message of mié jun 15 12:53:59 -0400 2011:
> 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.
The catalog change takes place in pg_constraint, so I'm not sure that
it'd cause the sort of event we need. I'm testing whether adding a call
to CacheInvalidateRelcache in the appropriate place works.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-06-15 17:12:45 | Re: bad posix_fadvise support causes initdb to exit ungracefully |
| Previous Message | Simon Riggs | 2011-06-15 17:03:59 | Strict Set Returning Functions |