| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Robert Treat <rob(at)xzilla(dot)net> |
| Cc: | Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, maciek(at)sakrejda(dot)org, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add mode column to pg_stat_progress_vacuum |
| Date: | 2025-11-20 07:28:48 |
| Message-ID: | CAA5RZ0vvziut9O-xr+S+d5A3ithpBJT1UkG1KPqOwhjT9b-gfw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | BharatDB | 2025-11-20 07:30:06 | [PATCH] Expose checkpoint timestamp and duration in pg_stat_checkpointer |
| Previous Message | Thomas Munro | 2025-11-20 07:16:34 | Re: Trying out <stdatomic.h> |