Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 8a9b72c

Browse files
committed
Fix grammar in README.tuplock
Author: Brad DeJong Discussion: https://postgr.es/m/CAJnrtnxrA4FqZi0Z6kGPQKMiZkWv2xxgSDQ+hv1jDrf8WCKjjw@mail.gmail.com
1 parent 3e32109 commit 8a9b72c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/backend/access/heap/README.tuplock

+4-4
Original file line numberDiff line numberDiff line change
@@ -45,10 +45,10 @@ and modifications which might alter the tuple's key. This is the lock that is
4545
implicitly taken by UPDATE operations which leave all key fields unchanged.
4646
SELECT FOR SHARE obtains a shared lock which prevents any kind of tuple
4747
modification. Finally, SELECT FOR KEY SHARE obtains a shared lock which only
48-
prevents tuple removal and modifications of key fields. This last mode
49-
implements a mode just strong enough to implement RI checks, i.e. it ensures
50-
that tuples do not go away from under a check, without blocking when some
51-
other transaction that want to update the tuple without changing its key.
48+
prevents tuple removal and modifications of key fields. This lock level is
49+
just strong enough to implement RI checks, i.e. it ensures that tuples do not
50+
go away from under a check, without blocking transactions that want to update
51+
the tuple without changing its key.
5252

5353
The conflict table is:
5454

0 commit comments

Comments
 (0)