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

Re: plpython crash (PG 92)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Asif Naeem <asif(dot)naeem(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: plpython crash (PG 92)
Date: 2012-05-02 18:04:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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.

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2012-05-02 18:14:31
Subject: Re: online debloatification (was: extending relations more efficiently)
Previous:From: Gabriele BartoliniDate: 2012-05-02 17:53:21
Subject: Re: Patch pg_is_in_backup()

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