database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-17 06:41:09 +03:00
Code Activity

Fix grammar in README.tuplock

Browse Source 
Author: Brad DeJong
Discussion: https://postgr.es/m/CAJnrtnxrA4FqZi0Z6kGPQKMiZkWv2xxgSDQ+hv1jDrf8WCKjjw@mail.gmail.com
This commit is contained in:
Alvaro Herrera
2018-07-27 10:56:30 -04:00
parent 3e32109049
commit 8a9b72c3ea
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/backend/access/heap/README.tuplock
View File

@ -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. implicitly taken by UPDATE operations which leave all key fields unchanged.
SELECT FOR SHARE obtains a shared lock which prevents any kind of tuple 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 modification. Finally, SELECT FOR KEY SHARE obtains a shared lock which only
prevents tuple removal and modifications of key fields. This last mode prevents tuple removal and modifications of key fields. This lock level is
implements a mode just strong enough to implement RI checks, i.e. it ensures just strong enough to implement RI checks, i.e. it ensures that tuples do not
that tuples do not go away from under a check, without blocking when some go away from under a check, without blocking transactions that want to update
other transaction that want to update the tuple without changing its key. the tuple without changing its key.
The conflict table is: The conflict table is: