diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2018-07-27 10:56:30 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2018-07-27 10:56:30 -0400 |
| commit | 8a9b72c3ea40c1ca1094bdcfd21a5263aee806f2 (patch) | |
| tree | 1781db78d9e6c23e08e0c2feedc2bbe812731c0e /src | |
| parent | 3e32109049142d3b6adb3b45afd0bb0dea24c23a (diff) | |
| download | postgresql-8a9b72c3ea40c1ca1094bdcfd21a5263aee806f2.tar.gz postgresql-8a9b72c3ea40c1ca1094bdcfd21a5263aee806f2.zip | |
Fix grammar in README.tuplock
Author: Brad DeJong
Discussion: https://postgr.es/m/CAJnrtnxrA4FqZi0Z6kGPQKMiZkWv2xxgSDQ+hv1jDrf8WCKjjw@mail.gmail.com
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/access/heap/README.tuplock | 8 |
1 files 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: |