aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2020-03-31 17:52:48 -0400
committerBruce Momjian <bruce@momjian.us>2020-03-31 17:52:48 -0400
commite564c17d2aa283262bc8ee5a12bdd5ce70fa2afd (patch)
treeaa3a248dc215c710cf2729f2f2223fa77c40adbc
parent6a4c58158bc01ef6452b0dcb3888d8e7994f0f35 (diff)
downloadpostgresql-e564c17d2aa283262bc8ee5a12bdd5ce70fa2afd.tar.gz
postgresql-e564c17d2aa283262bc8ee5a12bdd5ce70fa2afd.zip
doc: restore wording from recent patch "rolled back to"
Reported-by: Tom Lane Discussion: https://postgr.es/m/31072.1585690490@sss.pgh.pa.us Backpatch-through: 9.5 - 12
-rw-r--r--doc/src/sgml/mvcc.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index 25f06604671..ba38d218a91 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -1041,7 +1041,7 @@ ERROR: could not serialize access due to read/write dependencies among transact
<para>
Once acquired, a lock is normally held until the end of the transaction. But if a
lock is acquired after establishing a savepoint, the lock is released
- immediately if the savepoint is rolled back. This is consistent with
+ immediately if the savepoint is rolled back to. This is consistent with
the principle that <command>ROLLBACK</command> cancels all effects of the
commands since the savepoint. The same holds for locks acquired within a
<application>PL/pgSQL</application> exception block: an error escape from the block