On Thu, Oct 31, 2024 at 11:49 AM Peter Geoghegan <p...@bowt.ie> wrote: > The emphasis on the work that one particular VACUUM operation > performed doesn't seem like the most relevant thing to users (I get > why you'd care about it in the context of your work, though). What > matters to users is that the overall picture over time is one where > VACUUM doesn't leave an excessive number of pages > not-all-frozen-in-VM.
I don't see it quite the same way. I agree that what users are really concerned about is the excessive number of unfrozen pages in the VM. But that's not the question here. The question is what should log_autovacuum_min_duration log. And I think it should log what the vacuum itself did, not what the state of the table ended up being around the time the vacuum ended. And I think there is certainly a use case for knowing how much work of each particular kind vacuum did. You might for example be trying to judge whether a particular vacuum was useless. Knowing the cumulative state of the table around the time the vacuum finished doesn't help you figure that out; a count of how much work the vacuum itself did does. -- Robert Haas EDB: http://www.enterprisedb.com
