postgres.git / summary / log / commit / refs

commit    b9d94670c1d9b9a6604bb5cd80f77e93aee4e776
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Tue Mar 31 21:52:48 2020 +0000
First released in: 9.5.22, 9.6.18, 10.13, 11.8, 12.3

    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


 doc/src/sgml/mvcc.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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


[parent: 5e6a44e47f73]