Hi,
I’ve added some changes to one of the approaches and also did additional cleanup and stabilization work on the vacuum statistics tests. Specifically:
- I moved the vacuum statistics tests into the tests tab and made them more stable. For slower machines, vacuum is now triggered inside the statistics wait function. Previously, some backends didn’t have enough time to release the lock, which could lead to differences because the vacuum hadn’t fully completed yet.
- I also ran the backend tests and fixed a couple of minor issues along the way.
- I ran pgindent to clean up and normalize the formatting.
For now, I’ve temporarily removed collecting statistics related to database-level errors when vacuum is forced to stop. I’m currently stuck on how to properly expose statistics for cluster-level objects, since their dbid is 0.
At the moment, only the second test still looks odd, and I haven’t fully figured out why yet. It seems like aggressive vacuum can no longer be triggered the same way as before with the current gucs, but I’m still investigating this.
Best regards,
Alena Rybakina