On Friday 30 April 2010 23:54:16 Andres Freund wrote:
> On Friday 30 April 2010 20:09:48 Tom Lane wrote:
> > Andres Freund <andres(at)anarazel(dot)de> writes:
> > > On Friday 30 April 2010 19:39:32 Tom Lane wrote:
> > >> 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.
> > Here's the patch I'm planning to apply --- working it back into the
> > back branches now.
> The one I measured was 9.0 only:
> Found by running something like:
> while true; do echo 'DO LANGUAGE plpythonu $$import
> gc;gc.collect();plpy.execute("SELECT unknown"); $$;';done|psql -h /tmp -p
> 5433 postgres
Actually this one is also visible by 'SELECT 1' which is kinda obivous with
the above diff I guess - but I wanted to mention it for completeness.
In response to
pgsql-bugs by date
|Next:||From: Vladimir Kokovic||Date: 2010-05-01 02:36:18|
|Subject: CVS build problem - make world target|
|Previous:||From: Andres Freund||Date: 2010-04-30 21:54:16|
|Subject: Re: plpython memory leak uppon empty resultsets in all versions|