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
What is benefit of DO command in PLpgSQL? Looks bizarre for me.
Reards
Pavel
-- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services