Comments on: PostgreSQL: Increase the speed of UPDATE query using HOT UPDATE (Heap only tuple) https://www.dbrnd.com/2016/12/postgresql-increase-the-speed-of-update-query-using-hot-update-heap-only-tuple-mvcc-fill-factor-vacuum-fragmentation/ BIGData | NoSQL | MSSQL | MySQL | PostgreSQL Wed, 03 Apr 2019 00:07:50 +0000 hourly 1 https://wordpress.org/?v=7.0.4 By: Jude https://www.dbrnd.com/2016/12/postgresql-increase-the-speed-of-update-query-using-hot-update-heap-only-tuple-mvcc-fill-factor-vacuum-fragmentation/#comment-6944 Wed, 03 Apr 2019 00:07:50 +0000 https://www.dbrnd.com/?p=3708#comment-6944 Hi Anvesh

I am new to postgres , so please mind my ignorance. HOT updates are a good thing but it will not happen if the updated column(s) are part of an index.

If the updated column is part of an index
– Will the updated tuple be moved to a new page always? and if it is moved, will it got the next available page or moved the bottom of the table.
Will you please be able to describe the impact on the related indexes. ( Will the index tree and index data be changed in the same transaction?)
– If there is PK for the table, will the unique index created as part of the PK be impacted.

Cheers
Jude

]]>