Re: [Slony1-general] Re: dangling lock information? - Mailing list pgsql-hackers

From Andreas Pflug
Subject Re: [Slony1-general] Re: dangling lock information?
Date
Msg-id 4314D14D.2070205@pse-consulting.de
Whole thread Raw
In response to Re: [Slony1-general] Re: dangling lock information?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
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.

Regards,
Andreas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Intermittent stats test failures on buildfarm
Next
From: Jeff MacDonald
Date:
Subject: Re: problems installing pgsql on rh9 box