Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit8a9b72c

Browse files
committed
Fix grammar in README.tuplock
Author: Brad DeJongDiscussion:https://postgr.es/m/CAJnrtnxrA4FqZi0Z6kGPQKMiZkWv2xxgSDQ+hv1jDrf8WCKjjw@mail.gmail.com
1 parent3e32109 commit8a9b72c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

‎src/backend/access/heap/README.tuplock

Lines changed: 4 additions & 4 deletions
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. Thislast mode
49-
implements a modejust strong enough to implement RI checks, i.e. it ensures
50-
that tuples do notgo away from under a check, without blockingwhen some
51-
other transaction that want to updatethe tuple without changing its key.
48+
prevents tuple removal and modifications of key fields. Thislock 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 blockingtransactions that want to update
51+
the tuple without changing its key.
5252

5353
The conflict table is:
5454

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp