NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commite95d550

committed

Fix comment on when HOT update is possible.

The conditions listed in this comment have changed several times, and atsome 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 andmaster, so fix in all those versions.

1 parent7d9eca5 commite95d550Copy full SHA for e95d550

File tree

1 file changed

-1

lines changed

src/backend/access/heap
- heapam.c

1 file changed

-1

lines changed

`‎src/backend/access/heap/heapam.c`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -3587,7 +3587,7 @@ heap_update(Relation relation, ItemPointer otid, HeapTuple newtup,`
`3587`	`3587`	`* Since the new tuple is going into the same page, we might be able`
`3588`	`3588`	`* to do a HOT update. Check if any of the index columns have been`
`3589`	`3589`	`* changed. If the page was already full, we may have skipped checking`
`3590`		`- * for index columns. If so, HOT update is possible.`
	`3590`	`+ * for index columns, and also can't do a HOT update.`
`3591`	`3591`	`*/`
`3592`	`3592`	`if (hot_attrs_checked&& !bms_overlap(modified_attrs,hot_attrs))`
`3593`	`3593`	`use_hot_update= true;`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commite95d550

File tree

1 file changed

1 file changed

`‎src/backend/access/heap/heapam.c`

0 commit comments