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
> This area appears to be shy a regression test case or two, in any event.
Fixed like that.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2012-05-02 18:14:31|
|Subject: Re: online debloatification (was: extending relations more efficiently)|
|Previous:||From: Gabriele Bartolini||Date: 2012-05-02 17:53:21|
|Subject: Re: Patch pg_is_in_backup()|