Re: Add mode column to pg_stat_progress_vacuum

From: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add mode column to pg_stat_progress_vacuum
Date: 2025-10-24 07:06:12
Message-ID: CAOzEurTrwJ5+0=Kt_AjnQhsXBY0_22J4=LJLBiim-6c-W+_9Cg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 16, 2025 at 2:17 PM Michael Paquier <michael(at)paquier(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shinya Kato 2025-10-24 07:14:26 Re: Add mode column to pg_stat_progress_vacuum
Previous Message Daniel Gustafsson 2025-10-24 06:58:11 Re: Remove specific \r\n code in TAP for Windows