Request a Demo
Home   >   mailing lists

Re: Curing plpgsql's memory leaks for statement-lifespan values - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Curing plpgsql's memory leaks for statement-lifespan values
Date
Msg-id [email protected]
Whole thread Raw
In response to Re: Curing plpgsql's memory leaks for statement-lifespan values  (Tom Lane <[email protected]>)
Responses Re: Curing plpgsql's memory leaks for statement-lifespan values
Re: Curing plpgsql's memory leaks for statement-lifespan values
List pgsql-hackers
Tree view 
Tom Lane wrote:

> Although this is in principle a bug fix, it's invasive enough that I'd
> be pretty hesitant to back-patch it, or even to stick it into HEAD
> post-beta.  I'm inclined to sign it up for the next commitfest instead.

Do we have a backpatchable fix for the reported problem?  If so, then it
seems a good tradeoff to install this more invasive fix in HEAD only and
apply the simpler fix to back branches.  Otherwise, is the proposal to
leave the bug unfixed in back branches?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: No longer possible to query catalogs for index capabilities?
Next
From: Alvaro Herrera
Date:
Subject: Re: Curing plpgsql's memory leaks for statement-lifespan values