Re: Memory leak with CALL to Procedure with COMMIT.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: Memory leak with CALL to Procedure with COMMIT.
Date: 2018-07-23 07:06:44
Message-ID: 20180723070644.GJ2854@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-07-23 07:16:18 Re: [HACKERS] Restricting maximum keep segments by repslots
Previous Message 임명규 2018-07-23 07:04:42 [Proposal] Add accumulated statistics for wait event