Skip to content

P
Postgres FD Implementation
Commit 8a9b72c3 authored by Alvaro Herrera's avatar Alvaro Herrera
Browse files
Options

Fix grammar in README.tuplock 

Author: Brad DeJong
Discussion: https://postgr.es/m/CAJnrtnxrA4FqZi0Z6kGPQKMiZkWv2xxgSDQ+hv1jDrf8WCKjjw@mail.gmail.com
parent 3e321090
Show whitespace changes
Inline Side-by-side
Showing with 4 additions and 4 deletions
src/backend/access/heap/README.tuplock
View file @ 8a9b72c3
...@@ -45,10 +45,10 @@ and modifications which might alter the tuple's key. This is the lock that is ...@@ -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:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment