Re: [BUGS] BUG #9223: plperlu result memory leak

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Sergey Burladyan <eshkinkot(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #9223: plperlu result memory leak
Date: 2014-03-06 02:59:32
Message-ID: CAFaPBrRpYxAK8KFqQh6kxaSr9S0O0nkRfwPCgEJLEfORZM-ouA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, Mar 5, 2014 at 12:55 PM, Alex Hunsaker <badalex(at)gmail(dot)com> wrote:
> On Wed, Mar 5, 2014 at 12:22 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
>
>> Can I bug you into verifying what supported releases need this patch,
>> and to which does it backpatch cleanly? And if there's any to which it
>> doesn't, can I further bug you into providing one that does?
>
> Sure! Not bugging at all. I'll dig into this in a few hours.

This will apply cleanly all the way to REL9_2_STABLE. It applies (with
fuzz, but cleanly to REL9_1). REL9_0 does this completely differently
and so does not have this leak.

Thanks!

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2014-03-06 06:25:11 Re: BUG #9398: DELETE refering to a materialized view produces "cannot lock rows in materialized view" error
Previous Message Tom Lane 2014-03-05 23:46:44 Re: BUG #9398: DELETE refering to a materialized view produces "cannot lock rows in materialized view" error

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-03-06 03:33:09 Re: Comment - uniqueness of relfilenode
Previous Message Florian Pflug 2014-03-06 02:27:42 Re: [PATCH] Negative Transition Aggregate Functions (WIP)