Horton

Re: Vacuum statistics

Alena Rybakina <a.rybakina@postgrespro.ru>

View thread
From: Alena Rybakina <a.rybakina@postgrespro.ru>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Jim Nasby <jnasby@upgrade.com>, Ilia Evdokimov <ilya.evdokimov@tantorlabs.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>, a.lepikhov@postgrespro.ru, Sami Imseih <samimseih@gmail.com>
Date: 2025-02-04T15:49:43Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Move wal_buffers_full from PgStat_PendingWalStats to WalUsage

Attachments

On 04.02.2025 18:22, Alena Rybakina wrote:
>
>>   Also, should pgstat_track_vacuum_statistics also affect
>> per database statistics?
>
> According to my original idea, I thought that we could collect 
> extended statistics on relationships depending on whether the hook is 
> enabled, and always on databases. This will help us to constantly 
> collect statistics on the vacuum and notice when something is wrong 
> and at the same time not very expensive: there are much fewer 
> databases compared to the same relationships and there are much fewer 
> statistics there. You can introduce an additional hook that disables 
> all collection of vacuum statistics. This patch can be seen here for 
> the 17th version of the patch [0], I have not yet started adding it, 
> since we did not come to an agreement.
I added this version as 
"v19-0003.2-extended-vacuum-statistics.patch.no-cbot"

-- 
Regards,
Alena Rybakina
Postgres Professional