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

Commit77d2c00

Browse files
committed
Reword some unclear comments
1 parentf5d54ef commit77d2c00

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
@@ -3983,7 +3983,7 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
39833983

39843984
/*
39853985
* To prevent concurrent sessions from updating the tuple, we have to
3986-
* temporarily mark it locked, while we release the lock.
3986+
* temporarily mark it locked, while we release thepage-levellock.
39873987
*
39883988
* To satisfy the rule that any xid potentially appearing in a buffer
39893989
* written out to disk, we unfortunately have to WAL log this
@@ -3995,8 +3995,9 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
39953995

39963996
/*
39973997
* Compute xmax / infomask appropriate for locking the tuple. This has
3998-
* to be done separately from the lock, because the potentially
3999-
* created multixact would otherwise be wrong.
3998+
* to be done separately from the combo that's going to be used for
3999+
* updating, because the potentially created multixact would otherwise
4000+
* be wrong.
40004001
*/
40014002
compute_new_xmax_infomask(HeapTupleHeaderGetRawXmax(oldtup.t_data),
40024003
oldtup.t_data->t_infomask,

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp