| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | 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-14 13:35:14 |
| Message-ID: | a36e8421-6594-c051-7fa8-f0695d164ec1@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The commit that started this is
commit 59a85323d9d5927a852939fa93f09d142c72c91a
Author: Peter Eisentraut <peter_e(at)gmx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2018-08-14 14:05:29 | Re: logical decoding / rewrite map vs. maxAllocatedDescs |
| Previous Message | Peter Eisentraut | 2018-08-14 13:19:43 | InsertPgAttributeTuple() and attcacheoff |