From: | Sami Imseih <samimseih(at)gmail(dot)com> |
---|---|
To: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru> |
Cc: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: POC: track vacuum/analyze cumulative time per relation |
Date: | 2025-01-10 16:21:56 |
Message-ID: | CAA5RZ0uVgHa2JLSEsq8jDMRdUmyfhz9gg0UHhx0g2zoB7h_faA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 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.
>
> The purpose of total_time is to be able to calculate the average
> time of a vacuum per relation from pg_stat_all_tables (by
> total_time/vacuum_count) This is useful on its own to be able to
> trend slow downs of vacuum ( or improvements after vacuum tuning )
> for specific relations.
>
> The work going into [1] is more detailed and will be useful
> for deep dive investigations.In short, I think both proposals
> have merit.
Missed this point in my last reply. This patch also tracks
(auto)analyze per relation cumulative timing which can
be useful along with (auto)analyze_count to derive
the average.
Regards,
Sami
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2025-01-10 16:51:40 | Re: use a non-locking initial test in TAS_SPIN on AArch64 |
Previous Message | Tomas Vondra | 2025-01-10 16:18:12 | Re: Adjusting hash join memory limit to handle batch explosion |