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

From Jan Urbański
Subject Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is
Date
Msg-id 4D906125.8020306@wulczer.org
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is
List pgsql-hackers
On 28/03/11 04:31, Tom Lane wrote:
> David Fetter <david@fetter.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.

FWIW I executed

do $$ plpy.execute("select 1 from pg_class") $$ language plpythonu;

10k times in a session and the backend grew a lot in memory and never
released it. I can't offhand see where the memory went, I'll try to
investigate in the evening.

Cheers,
Jan


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Additional options for Sync Replication
Next
From: Heikki Linnakangas
Date:
Subject: Re: Replication server timeout patch