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

Commit1924ef4

Browse files
committed
Reword some unclear comments
1 parenteca2f8a commit1924ef4

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

39313931
/*
39323932
* To prevent concurrent sessions from updating the tuple, we have to
3933-
* temporarily mark it locked, while we release the lock.
3933+
* temporarily mark it locked, while we release thepage-levellock.
39343934
*
39353935
* To satisfy the rule that any xid potentially appearing in a buffer
39363936
* written out to disk, we unfortunately have to WAL log this
@@ -3942,8 +3942,9 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
39423942

39433943
/*
39443944
* Compute xmax / infomask appropriate for locking the tuple. This has
3945-
* to be done separately from the lock, because the potentially
3946-
* created multixact would otherwise be wrong.
3945+
* to be done separately from the combo that's going to be used for
3946+
* updating, because the potentially created multixact would otherwise
3947+
* be wrong.
39473948
*/
39483949
compute_new_xmax_infomask(HeapTupleHeaderGetRawXmax(oldtup.t_data),
39493950
oldtup.t_data->t_infomask,

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp