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 | f0862643ee6ba04a719f71c1d739a5395525b812 (patch) | |
| tree | cbcbd96e55fdfeec1f0cff5f3c9243382fea02c1 | |
| parent | 3f8276a2f04cf3c27fb4ee6647801add42d55218 (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 95465d581b6..ecff9474c8e 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 |