Reword some unclear comments

diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c
index 23139e46cbbbb1aa24c844f3f657274da5ac7217..e6caa4e9b6cea4d0cf5079454ef8824f0e4c6da9 100644 (file)
--- a/src/backend/access/heap/heapam.c
+++ b/src/backend/access/heap/heapam.c
@@ -3706,7 +3706,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
@@ -3718,8 +3718,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,