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

From Maciek Sakrejda
Subject Re: Add mode column to pg_stat_progress_vacuum
Date
Msg-id CAOtHd0DTL471tpDKH4H37oVQ_X90w0b2ekcrPqmUmWPxV+SRyg@mail.gmail.com
Whole thread Raw
In response to Re: Add mode column to pg_stat_progress_vacuum  (Shinya Kato <shinya11.kato@gmail.com>)
List pgsql-hackers
On Tue, Nov 18, 2025, 21:10 Shinya Kato <shinya11.kato@gmail.com> wrote:
On Wed, Nov 19, 2025 at 9:04 AM Masahiko Sawada
<sawada.mshk@gmail.com> > > Fixed, but I have a comment. I noticed
minor wording inconsistencies,
> > e.g., 'started' vs. 'initiated' and 'due to' vs. 'because of'. Should
> > I unify these terms?
>
> +1

It seems the inconsistency between 'started' and 'initiated' has not
been resolved. Come to think of it, since the column name is
triggerd_by, I think it would be best to standardize on 'triggered'. I
have attached a patch to fix this.

I'm late to the discussion, but have you considered just "trigger" for the column name? It's shorter and just as clear. 

In any case, thanks for working on and reviewing this—it's a handy addition!

Thanks, 
Maciek

pgsql-hackers by date:

Previous
From: Jim Jones
Date:
Subject: Re: [PATCH] Add pg_get_tablespace_ddl() function to reconstruct CREATE TABLESPACE statement
Next
From: Peter Eisentraut
Date:
Subject: Re: Reorganize GUC structs