@@ -3930,7 +3930,7 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
3930
3930
3931
3931
/*
3932
3932
* 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-level lock.
3934
3934
*
3935
3935
* To satisfy the rule that any xid potentially appearing in a buffer
3936
3936
* written out to disk, we unfortunately have to WAL log this
@@ -3942,8 +3942,9 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,
3942
3942
3943
3943
/*
3944
3944
* 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.
3947
3948
*/
3948
3949
compute_new_xmax_infomask (HeapTupleHeaderGetRawXmax (oldtup .t_data ),
3949
3950
oldtup .t_data -> t_infomask ,