PostgreSQL FILLFACTOR & HOT updates
Modern versions of Postgres are able to perform HOT (Heap Only Tuple) updates. A HOT update occurs when a new version of a row can be stored on the same page as the original version, without the need to move the row to a new page.
(…)
For HOT updates, Postgres will skip the update to the index IF you aren’t updating the index key.
By skipping the index update step, HOT updates reduce the amount of disk I/O and CPU processing required for an update operation, leading to better performance, especially for tables with large indexes or frequent updates.
https://www.crunchydata.com/blog/postgres-performance-boost-hot-updates-and-fill-factor
Modern versions of Postgres are able to perform HOT (Heap Only Tuple) updates. A HOT update occurs when a new version of a row can be stored on the same page as the original version, without the need to move the row to a new page.
(…)
For HOT updates, Postgres will skip the update to the index IF you aren’t updating the index key.
By skipping the index update step, HOT updates reduce the amount of disk I/O and CPU processing required for an update operation, leading to better performance, especially for tables with large indexes or frequent updates.
https://www.crunchydata.com/blog/postgres-performance-boost-hot-updates-and-fill-factor