| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | Robert Treat <rob(at)xzilla(dot)net>, Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, maciek(at)sakrejda(dot)org, 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-24 23:12:39 |
| Message-ID: | CAD21AoAiMBrzO7hxU9fs0uNLxq_T+XjjhdvjQX6fRd5DTaronA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 19, 2025 at 11:28 PM Sami Imseih <samimseih(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-11-24 23:18:00 | Re: Remove useless casting to the same type |
| Previous Message | Andres Freund | 2025-11-24 22:24:46 | Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) |