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

From Nathan Bossart
Subject Re: Add mode column to pg_stat_progress_vacuum
Date
Msg-id aOU_G4qdOv_gG7DI@nathan
Whole thread Raw
In response to Re: Add mode column to pg_stat_progress_vacuum  (Robert Treat <rob@xzilla.net>)
Responses Re: Add mode column to pg_stat_progress_vacuum
Re: Add mode column to pg_stat_progress_vacuum
List pgsql-hackers
On Tue, Oct 07, 2025 at 11:50:46AM -0400, Robert Treat wrote:
> On Tue, Oct 7, 2025 at 11:04 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>> I wonder if we should also add "aggressive".
> 
> I don't think so. I feel like the point of the mode is to answer "why
> is this vacuum running" not "how is it operating under the hood".

To some extent, those are tied together.  For example, a failsafe vacuum is
an anti-wraparound vacuum that skips index vacuuming, etc.  And an
anti-wraparound vacuum implies an aggressive scan, but not vice versa.
There's also a separate parameter (vacuum_freeze_table_age) that controls
when vacuum decides to perform an aggressive scan, just like there exists a
parameter for anti-wraparound vacuums (autovacuum_freeze_max_age) and
failsafe vacuums (vacuum_failsafe_age).

-- 
nathan



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: comment for TwoPhaseGetOldestXidInCommit
Next
From: Matthias van de Meent
Date:
Subject: Re: Buffer locking is special (hints, checksums, AIO writes)