diff options
| author | Bruce Momjian <bruce@momjian.us> | 2020-03-31 17:52:48 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2020-03-31 17:52:48 -0400 |
| commit | a1e42d8cd90292ed4667b1cacfc503a1feca449f (patch) | |
| tree | c326237262616ac8a66d47dcfc8363fbe25e2577 | |
| parent | 8a2ad9de402a715686afb1cdcaf622b4ad4f8f4e (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
| -rw-r--r-- | doc/src/sgml/mvcc.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index ce00455ec2f..ee47fb60382 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -1034,7 +1034,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 |