Re: Add mode column to pg_stat_progress_vacuum - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: Add mode column to pg_stat_progress_vacuum
Date
Msg-id CAA5RZ0t5hrrYik1wrBK0EN19tkTcDvxy73mcFNoM92PgFhwHcg@mail.gmail.com
Whole thread Raw
In response to Re: Add mode column to pg_stat_progress_vacuum  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
> >  I wonder if we could be even more granular
> > for the "normal autovacuum" case and point to the reason the table was
> > chosen.  For example, was it the insert threshold, the update/delete
> > threshold, etc.?
>
> Sounds like reasonable information. I guess we might want to have such
> information in a cumulative statistics view but do you think it's
> better to have it in a dynamic statistics view?

+1 for this information in cumulative stats, on a per table level for sure.
I do think however the pg_stat_all_tables views is getting too wide
and moving new relation vacuum stats to a separate stats view will
be very useful.

--
Sami



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Add mode column to pg_stat_progress_vacuum
Next
From: Andres Freund
Date:
Subject: Re: Should we update the random_page_cost default value?