mirror of
https://github.com/postgres/postgres.git
synced 2025-05-03 22:24:49 +03:00
Reword some unclear comments
This commit is contained in:
parent
eca2f8a7dd
commit
1924ef4166
@ -3930,7 +3930,7 @@ l2:
|
|||||||
|
|
||||||
/*
|
/*
|
||||||
* To prevent concurrent sessions from updating the tuple, we have to
|
* To prevent concurrent sessions from updating the tuple, we have to
|
||||||
* temporarily mark it locked, while we release the lock.
|
* temporarily mark it locked, while we release the page-level lock.
|
||||||
*
|
*
|
||||||
* To satisfy the rule that any xid potentially appearing in a buffer
|
* To satisfy the rule that any xid potentially appearing in a buffer
|
||||||
* written out to disk, we unfortunately have to WAL log this
|
* written out to disk, we unfortunately have to WAL log this
|
||||||
@ -3942,8 +3942,9 @@ l2:
|
|||||||
|
|
||||||
/*
|
/*
|
||||||
* Compute xmax / infomask appropriate for locking the tuple. This has
|
* Compute xmax / infomask appropriate for locking the tuple. This has
|
||||||
* to be done separately from the lock, because the potentially
|
* to be done separately from the combo that's going to be used for
|
||||||
* created multixact would otherwise be wrong.
|
* updating, because the potentially created multixact would otherwise
|
||||||
|
* be wrong.
|
||||||
*/
|
*/
|
||||||
compute_new_xmax_infomask(HeapTupleHeaderGetRawXmax(oldtup.t_data),
|
compute_new_xmax_infomask(HeapTupleHeaderGetRawXmax(oldtup.t_data),
|
||||||
oldtup.t_data->t_infomask,
|
oldtup.t_data->t_infomask,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user