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

Commit962b26b

Browse files
committed
Reword some unclear comments
1 parenta5915db commit962b26b

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

‎src/backend/access/heap/heapam.c

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3443,7 +3443,7 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
34433443

34443444
/*
34453445
* To prevent concurrent sessions from updating the tuple, we have to
3446-
* temporarily mark it locked, while we release the lock.
3446+
* temporarily mark it locked, while we release thepage-levellock.
34473447
*
34483448
* To satisfy the rule that any xid potentially appearing in a buffer
34493449
* written out to disk, we unfortunately have to WAL log this
@@ -3455,8 +3455,9 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
34553455

34563456
/*
34573457
* Compute xmax / infomask appropriate for locking the tuple. This has
3458-
* to be done separately from the lock, because the potentially
3459-
* created multixact would otherwise be wrong.
3458+
* to be done separately from the combo that's going to be used for
3459+
* updating, because the potentially created multixact would otherwise
3460+
* be wrong.
34603461
*/
34613462
compute_new_xmax_infomask(HeapTupleHeaderGetRawXmax(oldtup.t_data),
34623463
oldtup.t_data->t_infomask,

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp