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 aOVkzVpXRvenZZ4T@nathan
Whole thread Raw
In response to Re: Add mode column to pg_stat_progress_vacuum  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Add mode column to pg_stat_progress_vacuum
List pgsql-hackers
On Tue, Oct 07, 2025 at 12:45:12PM -0500, Sami Imseih wrote:
> The vacuum command detail can now be determined from
> pg_stat_activity.query by joining with pg_stat_progress_vacuum, right?
> I don't see why this is not sufficient, especially because it already
> indicates how the vacuum was triggered, and the autovacuum activity
> message also tells you why it was triggered. We could perhaps add "due to
> failsafe" to the autovacuum activity message to explicitly show that reason.

Eh, IMHO requiring users to look for a certain substring in the query field
doesn't seem especially user-friendly to me.  (I was going to point out
that it's undocumented, too, but it is in fact documented [0].)

[0] https://www.postgresql.org/docs/current/routine-vacuuming.html#AUTOVACUUM

-- 
nathan



pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: split func.sgml to separated individual sgml files
Next
From: Greg Sabino Mullane
Date:
Subject: Re: Should we update the random_page_cost default value?