Re: plpython crash (PG 92) - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: plpython crash (PG 92)
Date
Msg-id 1335981899.29903.5.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: plpython crash (PG 92)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On lör, 2012-04-28 at 00:32 -0400, Tom Lane wrote:
> I'm inclined to think that the best fix is for
> PLy_spi_execute_fetch_result to copy the tupledesc into
> TopMemoryContext, not the current context.  This is a tad scary from a
> memory leakage standpoint, but I suppose that if python fails to recover
> the PLyResultObject, this isn't the only memory that's going to be
> leaked.
> 
> This area appears to be shy a regression test case or two, in any event.

Fixed like that.



pgsql-hackers by date:

Previous
From: Gabriele Bartolini
Date:
Subject: Re: Patch pg_is_in_backup()
Next
From: Jameison Martin
Date:
Subject: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap