Message-ID: <594fd111-8016-4f44-bc8c-e1a0d66f26f6@postgrespro.ru>
Date: Fri, 10 Jan 2025 17:37:26 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: POC: track vacuum/analyze cumulative time per relation
To: wenhui qiu <qiuwenhuifx@gmail.com>, Sami Imseih <samimseih@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
References: <CAA5RZ0uVOGBYmPEeGF2d1B_67tgNjKx_bKDuL+oUftuoz+=Y1g@mail.gmail.com>
 <CAGjGUAJEhvsjni3q5y0iGAptb6s5UpxKJiLj3A_1CUwGdrujdA@mail.gmail.com>
Content-Language: en-US
From: Alena Rybakina <a.rybakina@postgrespro.ru>
In-Reply-To: <CAGjGUAJEhvsjni3q5y0iGAptb6s5UpxKJiLj3A_1CUwGdrujdA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/594fd111-8016-4f44-bc8c-e1a0d66f26f6%40postgrespro.ru>
Precedence: bulk

Hi!

On 04.01.2025 06:41, wenhui qiu wrote:
> Hi Sami
>  Thank you for your path，it seems some path monitor vacuum status，Can 
> we synthesize their good ideas together。
>
I've been working on a patch that collects vacuum statistics since May 
[0]. It includes heap and index relation vacuum statistics, and of 
course, database vacuum statistics. We welcome reviews and any feedback!

It collects a bit more information than total_time, such as delay_time, 
buffer statistics, wal statistics, number of processed, skipped pages 
and tuples during vacuum operations, so
this information gives a complete picture of vacuum efficiency, because 
analyzing only total_time statistics does not give a complete picture of 
what vacuum did: was it cleaning almost huge index, cleaning tables or 
just sleeping.

[0] https://commitfest.postgresql.org/51/5012/

-- 
Regards,
Alena Rybakina
Postgres Professional