Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is
Date: 2011-03-28 02:31:41
Message-ID: 17997.1301279501@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

David Fetter <david(at)fetter(dot)org> writes:
> On Sun, Mar 27, 2011 at 04:51:13PM +0000, Tom Lane wrote:
>> Fix plpgsql to release SPI plans when a function or DO block is freed.

> Do the other PLs we ship need similar fixes?

Offhand I think the other PLs leave management of prepared plans to the
user. If there are any places where they cache plans behind the scenes,
maybe a similar fix would be appropriate.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-03-28 07:25:06 Re: pgsql: Fix plpgsql to release SPI plans when a function or DO block is
Previous Message Robert Haas 2011-03-28 01:36:42 pgsql: Typo fix in SSI docs.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-03-28 02:43:55 Re: Lock problem with autovacuum truncating heap
Previous Message Tom Lane 2011-03-28 02:28:27 Re: Lock problem with autovacuum truncating heap