Re: Transaction control in procedures - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Transaction control in procedures
Date
Msg-id 36b95cdc-f72c-15ec-f888-2ad18543e6cd@2ndquadrant.com
Whole thread Raw
In response to RE: Transaction control in procedures  (legrand legrand <legrand_legrand@hotmail.com>)
Responses Re: Transaction control in procedures  (Merlin Moncure <mmoncure@gmail.com>)
List 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


pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: bgwriter_lru_maxpages range in postgresql.conf
Next
From: Robert Haas
Date:
Subject: Re: bgwriter_lru_maxpages range in postgresql.conf