| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | legrand legrand <legrand_legrand(at)hotmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Transaction control in procedures |
| Date: | 2017-11-16 18:36:09 |
| Message-ID: | 36b95cdc-f72c-15ec-f888-2ad18543e6cd@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/16/17 07:04, legrand legrand wrote:
> We are just opening the "close cursors on/at commit" specification ;o)
>
> - MS SQL server: cursor_close_on_commit
> - Firebird: close_cursors_at_commit
> - DB2: "with hold" syntax
> - ...
>
> I think it a plus to support keeping opened cursors at commit time,
> but impacts have to be checked in details ...
I think the facilities to support this in PostgreSQL are already there.
We'd just have to tweak PL/pgSQL to make some of its internal portals
"held" and then clean them up manually at some later point. So I think
this is a localized detail, not a fundamental problem.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-11-16 19:10:30 | Re: bgwriter_lru_maxpages range in postgresql.conf |
| Previous Message | Jeff Janes | 2017-11-16 18:26:59 | bgwriter_lru_maxpages range in postgresql.conf |