Skip site navigation (1) Skip section navigation (2)

Re: plpython memory leak uppon empty resultsets in all versions

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: plpython memory leak uppon empty resultsets in all versions
Date: 2010-04-30 17:57:36
Message-ID: 201004301957.36366.andres@anarazel.de (view raw or flat)
Thread:
Lists: pgsql-bugs
Hi,

On Friday 30 April 2010 19:39:32 Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > plpython[u] leaks memory in PLy_spi_execute_fetch_result in the following
> 
> > snippet:
> Yeah.  There's a leak of the tuptable in the CATCH path, too.  Will fix.
Yes, theres even more than that (measured it) in the error case. Will have a 
look later today.

Andres

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-04-30 18:09:48
Subject: Re: plpython memory leak uppon empty resultsets in all versions
Previous:From: Claudio FreireDate: 2010-04-30 17:53:35
Subject: Re: BUG #5443: Undetected deadlock situation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group