Re: Memory leak with CALL to Procedure with COMMIT. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Memory leak with CALL to Procedure with COMMIT.
Date
Msg-id 20180723070644.GJ2854@paquier.xyz
Whole thread Raw
In response to Memory leak with CALL to Procedure with COMMIT.  (Prabhat Sahu <prabhat.sahu@enterprisedb.com>)
Responses Re: Memory leak with CALL to Procedure with COMMIT.  ("Jonathan S. Katz" <jkatz@postgresql.org>)
List pgsql-hackers
On Mon, Jul 23, 2018 at 12:19:12PM +0530, Prabhat Sahu wrote:
> While testing with PG procedure, I found a memory leak on HEAD, with below
> steps:
>
> postgres=# CREATE OR REPLACE PROCEDURE proc1(v1 INOUT INT)
> AS $$
> BEGIN
>  commit;
> END; $$ LANGUAGE plpgsql;
> CREATE PROCEDURE
>
> postgres=# call proc1(10);
> WARNING:  Snapshot reference leak: Snapshot 0x23678e8 still referenced
>  v1
> ----
>  10
> (1 row)

I can reproduce this issue on HEAD and v11, so an open item is added.
Peter, could you look at it?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Non-portable shell code in pg_upgrade tap tests
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots