So far, a nested CALL or DO in PL/pgSQL would not establish a context where transaction control statements were allowed. This 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. Reviewed-by: Tomas Vondra <tomas.vondra@2ndquadrant.com> |
||
---|---|---|
.. | ||
src | ||
KNOWN_BUGS | ||
MISSING_FEATURES | ||
Makefile | ||
TODO | ||
bug.template |