Heikki Linnakangas wrote:
Even for fields that are used in primary searches, HOT updates avoid
changing the disk block layout, and as reading from the disk is usually
the most expensive operation, the decisions shouldn't change much before
and after a HOT update compared to before and after a regular update.
Tom Lane wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
HOT greatly reduces the number of vacuums needed. That's good, that's
where the gains in throughput in longer I/O bound runs comes from.
But surely failing to auto-analyze after a HOT update is a bad thing.
Hmm, I suppose. I don't think we've spend any time thinking about how to
factor in HOT updates into the autovacuum and autoanalyze formulas yet.
I'd argue that HOT updates are not as significant as cold ones from
statistics point of view, though, because they don't change indexed
columns. HOT-updated fields are not likely used as primary search quals.
Mark Mielke <[EMAIL PROTECTED]>