| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Curing plpgsql's memory leaks for statement-lifespan values |
| Date: | 2016-07-25 21:19:19 |
| Message-ID: | 20160725211919.GA298355@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-07-25 21:22:58 | Re: Curing plpgsql's memory leaks for statement-lifespan values |
| Previous Message | Stephen Frost | 2016-07-25 21:09:23 | Re: No longer possible to query catalogs for index capabilities? |