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

From Jan Urbański
Subject Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is
Date
Msg-id 4D9449B5.4070000@wulczer.org
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is
List pgsql-hackers
On 31/03/11 07:35, Heikki Linnakangas wrote:
> 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?

Yeah, you're right, you can keep it on the stack.

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

That always confuses me, but I guess you're right, the variable does not
change, only the memory it points to.

Cheers,
Jan


pgsql-hackers by date:

Previous
From: 高增琦
Date:
Subject: Re: crash-safe visibility map, take four
Next
From: Heikki Linnakangas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Fix plpgsql to release SPI plans when a function or DO block is