@@ -3983,7 +3983,7 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
3983
3983
3984
3984
/*
3985
3985
* 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-level lock.
3987
3987
*
3988
3988
* To satisfy the rule that any xid potentially appearing in a buffer
3989
3989
* written out to disk, we unfortunately have to WAL log this
@@ -3995,8 +3995,9 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
3995
3995
3996
3996
/*
3997
3997
* 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.
4000
4001
*/
4001
4002
compute_new_xmax_infomask (HeapTupleHeaderGetRawXmax (oldtup .t_data ),
4002
4003
oldtup .t_data -> t_infomask ,