Reword some unclear comments

diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c
index 84b59c341006f400ac72f2c89a917eec25c31360..4327be86100b38b3fb8db53fbd5ce7ac0710512c 100644 (file)
--- a/src/backend/access/heap/heapam.c
+++ b/src/backend/access/heap/heapam.c
@@ -3930,7 +3930,7 @@ l2:
 
                /*
                 * 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
                 * 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
-                * to be done separately from the lock, because the potentially
-                * created multixact would otherwise be wrong.
+                * to be done separately from the combo that's going to be used for
+                * updating, because the potentially created multixact would otherwise
+                * be wrong.
                 */
                compute_new_xmax_infomask(HeapTupleHeaderGetRawXmax(oldtup.t_data),
                                                                  oldtup.t_data->t_infomask,