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:07:43 |
Message-ID: | CAA5RZ0tBsAa-CY=-z_VPjFvMRWnKLzkt0QAUQxUx+CO1-YiS8g@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.
[1] https://commitfest.postgresql.org/51/5012/
Regards,
Sami
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2025-01-10 16:18:12 | Re: Adjusting hash join memory limit to handle batch explosion |
Previous Message | Nathan Bossart | 2025-01-10 15:38:14 | Re: [PATCH] Hex-coding optimizations using SVE on ARM. |