Re: Memory leak with CALL to Procedure with COMMIT.

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
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:13:31
Message-ID: 2426fc50-666a-79df-e862-ee425bfd5bcd@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2018-08-27 21:15:42 Re: Memory leak with CALL to Procedure with COMMIT.
Previous Message Bradley DeJong 2018-08-27 20:51:28 Re[3]: Adding a note to protocol.sgml regarding CopyData