HOT Updates in Postgres

In the previous article we watched every UPDATE leave dead tuple behind. The same copy-on-write behaviour shows up from the operational angle in DELETEs are difficult . That&#x27;s the tradeoff of MVCC and on the heap alone it&#x27;s tolerable. The problem is the indexes. Every UPDATE in PostgreSQL potentially writes to every index on the table, even when the indexed columns didn&#x27;t change.…