postgres.git / summary / log / commit / refs

commit    8a9b72c3ea40c1ca1094bdcfd21a5263aee806f2
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Fri Jul 27 14:56:30 2018 +0000
First released in: 12.0

    Fix grammar in README.tuplock
    
    Author: Brad DeJong
    Discussion: https://postgr.es/m/CAJnrtnxrA4FqZi0Z6kGPQKMiZkWv2xxgSDQ+hv1jDrf8WCKjjw@mail.gmail.com


 src/backend/access/heap/README.tuplock | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/backend/access/heap/README.tuplock b/src/backend/access/heap/README.tuplock
index 10b8d78ab7e..b2f3a4ce909 100644
--- a/src/backend/access/heap/README.tuplock
+++ b/src/backend/access/heap/README.tuplock
@@ -45,10 +45,10 @@ and modifications which might alter the tuple's key. This is the lock that is
 implicitly taken by UPDATE operations which leave all key fields unchanged.
 SELECT FOR SHARE obtains a shared lock which prevents any kind of tuple
 modification. Finally, SELECT FOR KEY SHARE obtains a shared lock which only
-prevents tuple removal and modifications of key fields. This last mode
-implements a mode just strong enough to implement RI checks, i.e. it ensures
-that tuples do not go away from under a check, without blocking when some
-other transaction that want to update the tuple without changing its key.
+prevents tuple removal and modifications of key fields. This lock level is
+just strong enough to implement RI checks, i.e. it ensures that tuples do not
+go away from under a check, without blocking transactions that want to update
+the tuple without changing its key.
 
 The conflict table is:
 


[parent: 3e3210904914]