| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL nested CALL with transactions |
| Date: | 2018-03-16 01:57:39 |
| Message-ID: | 703c5198-22c1-31cd-399e-d078b5ce55fb@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/28/18 14:51, Peter Eisentraut wrote:
> So far, a nested CALL or DO in PL/pgSQL would not establish a context
> where transaction control statements were allowed. This patch fixes
> that by handling CALL and DO specially in PL/pgSQL, passing the
> atomic/nonatomic execution context through and doing the required
> management around transaction boundaries.
rebased patch
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-PL-pgSQL-Nested-CALL-with-transactions.patch | text/plain | 19.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-03-16 01:58:59 | Re: [HACKERS] MERGE SQL Statement for PG11 |
| Previous Message | leap | 2018-03-16 01:57:26 | Re:Re: Re: [submit code] I develop a tool for pgsql, how can I submit it |