Request a Demo
Home   >   mailing lists

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

From Masahiko Sawada
Subject Re: Add mode column to pg_stat_progress_vacuum
Date
Msg-id CAD21AoAiMBrzO7hxU9fs0uNLxq_T+XjjhdvjQX6fRd5DTaronA@mail.gmail.com
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
Tree view 
On Wed, Nov 19, 2025 at 11:28 PM Sami Imseih <samimseih@gmail.com> wrote:
>>
>> I'd +1 for triggered_by over just trigger, but I actually think
>> triggered_by should be avoided as well for the same reason (term
>> overload). We already use the verb "launch" as the word to describe
>> this action in the existing autovacuum docs, but I was unable to come
>> up with something that both sounded good and made sense for the manual
>> vacuum case, so now I would lean towards "initialized_by".
>
>
> What about “started_by” ? it’s unambiguous and consistent with other columns
> like “query_start” in pg_stat_activity.

"started_by" sounds reasonable to me.

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
Next
From: Jacob Champion
Date:
Subject: Re: Remove useless casting to the same type