Re: Memory leak with CALL to Procedure with COMMIT.

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory leak with CALL to Procedure with COMMIT.
Date: 2018-08-27 21:15:42
Message-ID: 886E8858-771D-4A75-B3A6-CC969AF99FD3@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> On Aug 27, 2018, at 5:13 PM, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 23/08/2018 17:35, Jonathan S. Katz wrote:
>> Applied the patch against head. make check passed, all the tests I ran
>> earlier in this thread passed as well.
>>
>> Reviewed the code - looks to match above reasoning, and comments
>> are clear.
>>
>> From my perspective it looks good, but happy to hear from someone
>> more familiar than me with this area of the code.
>
> committed

Awesome, thank you! I’ve removed this from the Open Items list.

Jonathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2018-08-27 22:05:16 Re: FailedAssertion on partprune
Previous Message Peter Eisentraut 2018-08-27 21:13:31 Re: Memory leak with CALL to Procedure with COMMIT.