On 28/03/11 04:31, Tom Lane wrote:
> David Fetter <da...@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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
