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

From Shinya Kato
Subject Re: Add mode column to pg_stat_progress_vacuum
Date
Msg-id CAOzEurTrwJ5+0=Kt_AjnQhsXBY0_22J4=LJLBiim-6c-W+_9Cg@mail.gmail.com
Whole thread Raw
In response to Re: Add mode column to pg_stat_progress_vacuum  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Thu, Oct 16, 2025 at 2:17 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Thu, Oct 09, 2025 at 10:07:17AM -0500, Sami Imseih wrote:
> >> IIUC are you suggesting I add such a last_autovacuum_reason column to
> >> pg_stat_all_tables, which would be populated with one of the following
> >> values?
> >> - autovacuum_vacuum_threshold
> >> - autovacuum_vacuum_insert_threshold
> >> - autovacuum_freeze_max_age
> >> - autovacuum_multixact_freeze_max_age
> >
> > This should be a separate discussion. But, I would think the
> > counters will be n_aggressive, n_wraparound and n_failsafe.
>
> Depends, I guess (separate discussion it should be, but I count not
> resist).  If you had this information available in the cumulative
> stats, what should be a "correct" set of numbers, and what could be
> tuned to redirect the system so as it gets to a better set of numbers.
> Wraparound autovacuums, for one, don't seem really relevant
> to know about in an aggregated way.

Thank you for the comment. You’re right. Let’s set this discussion
aside for now and continue it in a separate thread.

--
Best regards,
Shinya Kato
NTT OSS Center



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Remove specific _\n code in TAP for Windows
Next
From: Shinya Kato
Date:
Subject: Re: Add mode column to pg_stat_progress_vacuum