summaryrefslogtreecommitdiff
path: root/doc/src
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
commitb9d94670c1d9b9a6604bb5cd80f77e93aee4e776 (patch)
tree7aa02387a60fcb15ef21c999a236400a0cef07d7 /doc/src
parent5e6a44e47f738373b686ad1b0bf8bcb40c6058c0 (diff)
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
Diffstat (limited to 'doc/src')
-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 c484435bb13..a4deeafa3ad 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</> cancels all effects of the
commands since the savepoint. The same holds for locks acquired within a
<application>PL/pgSQL</> exception block: an error escape from the block