From 862ef372d6b23629f93d4afc123ddd7d172501ac Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Sun, 8 Sep 2019 16:11:21 +0200 Subject: Fix behavior of AND CHAIN outside of explicit transaction blocks When using COMMIT AND CHAIN or ROLLBACK AND CHAIN not in an explicit transaction block, the previous implementation would leave a transaction block active in the ROLLBACK case but not the COMMIT case. To fix for now, error out when using these commands not in an explicit transaction block. This restriction could be lifted if a sensible definition and implementation is found. Bug: #15977 Author: fn ln Reviewed-by: Fabien COELHO --- doc/src/sgml/ref/commit.sgml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'doc/src/sgml/ref/commit.sgml') diff --git a/doc/src/sgml/ref/commit.sgml b/doc/src/sgml/ref/commit.sgml index e4169cd2c62..5f244cdd3c1 100644 --- a/doc/src/sgml/ref/commit.sgml +++ b/doc/src/sgml/ref/commit.sgml @@ -77,7 +77,8 @@ COMMIT [ WORK | TRANSACTION ] [ AND [ NO ] CHAIN ] Issuing COMMIT when not inside a transaction does - no harm, but it will provoke a warning message. + no harm, but it will provoke a warning message. COMMIT AND + CHAIN when not inside a transaction is an error. -- cgit v1.2.3