Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
doc: restore wording from recent patch "rolled back to"
authorBruce Momjian <bruce@momjian.us>
Tue, 31 Mar 2020 21:52:48 +0000 (17:52 -0400)
committerBruce Momjian <bruce@momjian.us>
Tue, 31 Mar 2020 21:52:48 +0000 (17:52 -0400)
Reported-by: Tom Lane
Discussion: https://postgr.es/m/31072.1585690490@sss.pgh.pa.us

Backpatch-through: 9.5 - 12

doc/src/sgml/mvcc.sgml

index 25f0660467186d0c0a743a60f74dbd1acdb42e7f..ba38d218a91a4e9e9e9d6422958085fe664a9d30 100644 (file)
@@ -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