Horton
Menu

Re: Add mode column to pg_stat_progress_vacuum

Sami Imseih <samimseih@gmail.com>

View thread
From: Sami Imseih <samimseih@gmail.com>
To: Robert Treat <rob@xzilla.net>
Cc: Shinya Kato <shinya11.kato@gmail.com>, maciek@sakrejda.org, Masahiko Sawada <sawada.mshk@gmail.com>, Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-11-20T07:28:48Z
Lists: pgsql-hackers 
> 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.

--
Sami Imseih
Amazon Web Services (AWS)

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add started_by column to pg_stat_progress_analyze view.

  2. Add mode and started_by columns to pg_stat_progress_vacuum view.