database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-03 22:24:49 +03:00
Code

Fix comment on when HOT update is possible.

Browse Source 
The conditions listed in this comment have changed several times, and at
some point the thing that the "if so" referred to was negated.

The text was OK up to 9.6. It was differently wrong in v10, v11 and
master, so fix in all those versions.
This commit is contained in:
Heikki Linnakangas 2019-05-14 13:06:28 +03:00
parent 7d9eca59cf
commit e95d550bbb
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/backend/access/heap/heapam.c
View File

@ -3587,7 +3587,7 @@ l2:
* Since the new tuple is going into the same page, we might be able * 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 * 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 * 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)) if (hot_attrs_checked && !bms_overlap(modified_attrs, hot_attrs))
use_hot_update = true; use_hot_update = true;