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

From: Jan Urbański <wulczer(at)wulczer(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Fetter <david(at)fetter(dot)org>, 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 10:21:25
Message-ID: 4D906125.8020306@wulczer.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 28/03/11 04:31, Tom Lane wrote:
> 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.

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2011-03-28 13:21:43 Re: pgsql: Fix plpgsql to release SPI plans when a function or DO block is
Previous Message Heikki Linnakangas 2011-03-28 07:25:06 Re: pgsql: Fix plpgsql to release SPI plans when a function or DO block is

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-03-28 10:49:15 Re: Replication server timeout patch
Previous Message Simon Riggs 2011-03-28 10:14:10 Re: Additional options for Sync Replication