Alvaro Herrera wrote:
>>Unfortunately, it's not at all obvious how to accomplish that :-(.
> I don't think it can be easily done with the current code. This is
> plpgsql code, right? There are some ways to cause recompilation for
> those, at least on the 8.1 code I'm looking at.
Well at least when a procedure is dropped, its cached plans could be
dropped as well (apparently the cache plan is located trough some kind
of hash, not the pg_proc.oid?). I do understand that the usual case, a
table oid changed while cached inside a procedure isn't easily
detectable because it would require dependency information generated
from procedure's source.
In response to
pgsql-hackers by date
|Next:||From: Chris Browne||Date: 2005-08-30 22:08:47|
|Subject: Re: [Slony1-general] Re: dangling lock information?|
|Previous:||From: Tom Lane||Date: 2005-08-30 20:36:16|
|Subject: Re: Intermittent stats test failures on buildfarm |