Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is
Date
Msg-id 4D94128C.9050604@enterprisedb.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is  (Jan Urbański <wulczer@wulczer.org>)
Responses Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is
List pgsql-hackers
On 30.03.2011 21:21, Jan Urbański wrote:
> Valgrind showed me the way. PFA a trivial patch to avoid leaking a
> PLyProcedure struct in inline blocks.

Hmm, any reason the PLyProcedure struct needs to be allocated in
TopMemoryContext in the first place? Could you palloc0 it in a
shorter-lived context, or even better, just allocate it in stack?

PS. I don't think the volatile qualifier in 'proc' is in necessary. The
variable is not changed in PG_TRY-block.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Brendan Jurd
Date:
Subject: Re: [GENERAL] Date conversion using day of week
Next
From: Heikki Linnakangas
Date:
Subject: Re: Replication server timeout patch