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

From Peter Eisentraut
Subject Re: Memory leak with CALL to Procedure with COMMIT.
Date
Msg-id a36e8421-6594-c051-7fa8-f0695d164ec1@2ndquadrant.com
Whole thread Raw
In response to Re: Memory leak with CALL to Procedure with COMMIT.  ("Jonathan S. Katz" <jkatz@postgresql.org>)
Responses Re: Memory leak with CALL to Procedure with COMMIT.
List pgsql-hackers
The commit that started this is

commit 59a85323d9d5927a852939fa93f09d142c72c91a
Author: Peter Eisentraut <peter_e@gmx.net>
Date:   Mon Jul 9 13:58:08 2018

    Add UtilityReturnsTuples() support for CALL

    This ensures that prepared statements for CALL can return tuples.

The change whether a statement returns tuples or not causes some
different paths being taking deep in the portal code that set snapshot
in different ways.  I haven't fully understood them yet.  I plan to post
more tomorrow.

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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: InsertPgAttributeTuple() and attcacheoff
Next
From: Tomas Vondra
Date:
Subject: Re: logical decoding / rewrite map vs. maxAllocatedDescs