git.postgresql.org Git - users/bernd/postgres.git/commit

projects / users / bernd / postgres.git / commit

summary | shortlog | log | commit | commitdiff | tree
(parent: c2d4eb1) | patch

author	Peter Eisentraut <peter_e@gmx.net>
	Sat, 24 Mar 2018 14:05:06 +0000 (10:05 -0400)
committer	Peter Eisentraut <peter_e@gmx.net>
	Wed, 28 Mar 2018 17:31:27 +0000 (13:31 -0400)
commit	d92bc83c48bdea9888e64cf1e2edbac9693099c9
tree	5cccf082581787b24af269613fb7b3cc4c4484d7	tree
parent	c2d4eb1b1fa252fd8c407e1519308017a18afed1	commit \| diff

PL/pgSQL: Nested CALL with transactions

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>

13 files changed:

doc/src/sgml/plpgsql.sgml		diff \| blob \| blame \| history
src/backend/executor/spi.c		diff \| blob \| blame \| history
src/backend/tcop/utility.c		diff \| blob \| blame \| history
src/include/executor/spi_priv.h		diff \| blob \| blame \| history
src/include/tcop/utility.h		diff \| blob \| blame \| history
src/pl/plpgsql/src/expected/plpgsql_transaction.out		diff \| blob \| blame \| history
src/pl/plpgsql/src/pl_exec.c		diff \| blob \| blame \| history
src/pl/plpgsql/src/pl_funcs.c		diff \| blob \| blame \| history
src/pl/plpgsql/src/pl_gram.y		diff \| blob \| blame \| history
src/pl/plpgsql/src/pl_handler.c		diff \| blob \| blame \| history
src/pl/plpgsql/src/pl_scanner.c		diff \| blob \| blame \| history
src/pl/plpgsql/src/plpgsql.h		diff \| blob \| blame \| history
src/pl/plpgsql/src/sql/plpgsql_transaction.sql		diff \| blob \| blame \| history

Bernd Helmle's repository