HOT Updates in Postgres

This site does not allow itself to be embedded. You can still read it on the original site — the toolbar below keeps your place in the directory.

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's the tradeoff of MVCC and on the heap alone it'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't change.…

Read on boringsql.com ↗