Re: Vacuum statistics
Alena Rybakina <lena.ribackina@yandex.ru>
From: Alena Rybakina <lena.ribackina@yandex.ru>
To: Alena Rybakina <a.rybakina@postgrespro.ru>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Alexander Korotkov <aekorotkov@gmail.com>,
Amit Kapila <amit.kapila16@gmail.com>, Jim Nasby <jnasby@upgrade.com>,
Bertrand Drouvot <bertranddrouvot.pg@gmail.com>,
Kirill Reshke <reshkekirill@gmail.com>, Andrei Zubkov <zubkov@moonset.ru>,
Masahiko Sawada <sawada.mshk@gmail.com>,
Melanie Plageman <melanieplageman@gmail.com>,
jian he <jian.universality@gmail.com>, Sami Imseih <samimseih@gmail.com>,
vignesh C <vignesh21@gmail.com>,
Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>
Date: 2026-02-28T22:20:00Z
Lists: pgsql-hackers
Attachments
- v27-0001-Introduce-new-statistics-tracking-the-number-of-time.patch (text/plain) patch v27-0001
- v27-0002-Add-machinery-for-grabbing-an-extended-vacuum-statis.patch (text/plain) patch v27-0002
- v27-0003-Add-documentation-about-the-system-views-that-are-us.patch (text/plain) patch v27-0003
On 21.12.2025 04:36, Alena Rybakina wrote: > > 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. > I have rebased the patch. I combined all the patches for implementing statistics on tables, indexes, and databases into one, creating a separate slot for them to collect and save statistics. > 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. > I fixed this problem - it works well now. Best regards, Alena Rybakina
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add relallfrozen to pg_class
- 99f8f3fbbc8f 18.0 cited
-
Move wal_buffers_full from PgStat_PendingWalStats to WalUsage
- eaf502747bac 18.0 cited