aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/commit.sgml
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2019-09-08 16:11:21 +0200
committerPeter Eisentraut <peter@eisentraut.org>2019-09-08 16:23:03 +0200
commit862ef372d6b23629f93d4afc123ddd7d172501ac (patch)
treef856f03468eb358ef1d0d156b06ec04ab34c0290 /doc/src/sgml/ref/commit.sgml
parent0e777462121bd5b892c1621903d1953a49437290 (diff)
downloadpostgresql-862ef372d6b23629f93d4afc123ddd7d172501ac.tar.gz
postgresql-862ef372d6b23629f93d4afc123ddd7d172501ac.zip
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 <emuser20140816@gmail.com> Reviewed-by: Fabien COELHO <coelho@cri.ensmp.fr>
Diffstat (limited to 'doc/src/sgml/ref/commit.sgml')
-rw-r--r--doc/src/sgml/ref/commit.sgml3
1 files changed, 2 insertions, 1 deletions
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 ]
<para>
Issuing <command>COMMIT</command> when not inside a transaction does
- no harm, but it will provoke a warning message.
+ no harm, but it will provoke a warning message. <command>COMMIT AND
+ CHAIN</command> when not inside a transaction is an error.
</para>
</refsect1>