Re: POC: track vacuum/analyze cumulative time per relation - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: POC: track vacuum/analyze cumulative time per relation
Date
Msg-id CAA5RZ0uVgHa2JLSEsq8jDMRdUmyfhz9gg0UHhx0g2zoB7h_faA@mail.gmail.com
Whole thread Raw
In response to Re: POC: track vacuum/analyze cumulative time per relation  (Sami Imseih <samimseih@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Adjusting hash join memory limit to handle batch explosion
Next
From: Nathan Bossart
Date:
Subject: Re: use a non-locking initial test in TAS_SPIN on AArch64