On 12/3/26 19:10, Alena Rybakina wrote:
On 12.03.2026 18:28, Andrei Lepikhov wrote:
In addition, it makes sense to discuss how these parameters are
supposed to be used. I see the following use cases:
1. Which tables have the most VM churn? - monitoring
rev_all_visible_pages normalised on the table size and its average
tuple width might expose the most suspicious tables (in terms of table
statistics).
2. DML Skew. Dividing rev_all_visible_pages by the number of tuple
updates/deletes, normalised by the average table and tuple sizes,
might indicate whether changes are localised within the table.
3. IndexOnlyScan effectiveness. Considering the speed of
rev_all_visible_pages change, normalised to the value of the
relallvisible statistic, we may detect tables where Index-Only Scan
might be inefficiently used.
I agree with all these points and I think we can add it in the
documentation.
I've updated the status to 'Ready for Committer'. Here’s what that means:
1. Patch v30-0001-* is ready to be committed. It’s straightforward
enough for this late stage of development. It’s now separate from the
original 'vacuum statistics' idea, which helps keep things simpler.
2. Patches 0002 and 0003 are not part of this commit set. I’m not sure
they should be included in PG19, and we can keep working on them.
--
regards, Andrei Lepikhov,
pgEdge
