Re: PL/pgSQL nested CALL with transactions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: PL/pgSQL nested CALL with transactions
Date
Msg-id 703c5198-22c1-31cd-399e-d078b5ce55fb@2ndquadrant.com
Whole thread Raw
In response to PL/pgSQL nested CALL with transactions  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: PL/pgSQL nested CALL with transactions  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: PL/pgSQL nested CALL with transactions  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List 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

pgsql-hackers by date:

Previous
From: leap
Date:
Subject: Re:Re: Re: [submit code] I develop a tool for pgsql, how can Isubmit it
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] MERGE SQL Statement for PG11