Fix comment on when HOT update is possible.

[postgresql] / src / backend / access / heap / heapam.c

diff --git a/src/backend/access/heap/heapam.c b/src/backend/access/heap/heapam.c
index d97cb4c642625cb83f2ab0de87bd2e945b7687d3..ec9853603fde49736e16ea3bdef691efca4d24b0 100644 (file)
--- a/src/backend/access/heap/heapam.c
+++ b/src/backend/access/heap/heapam.c
@@ -3587,7 +3587,7 @@ l2:
                 * Since the new tuple is going into the same page, we might be able
                 * to do a HOT update.  Check if any of the index columns have been
                 * changed. If the page was already full, we may have skipped checking
-                * for index columns. If so, HOT update is possible.
+                * for index columns, and also can't do a HOT update.
                 */
                if (hot_attrs_checked && !bms_overlap(modified_attrs, hot_attrs))
                        use_hot_update = true;