From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | MauMau <maumau307(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: sync process names between ps and pg_stat_activity |
Date: | 2017-09-20 01:14:41 |
Message-ID: | 16ccf418-b979-6bdd-2861-b1225d3f56d7@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/18/17 02:07, MauMau wrote:
> (1)
> In the following comment, it's better to change "wal sender process"
> to "walsender" to follow the modified name.
>
> - * postgres: wal sender process <user> <host> <activity>
> + * postgres: walsender <user> <host> <activity>
> *
> * To achieve that, we pass "wal sender process" as username and
> username
good catch
> (2)
> "WAL writer process" is used, not "walwriter", is used in postmaster.c
> as follows. I guess this is for natural language. Is this intended?
> I'm OK with either, though.
>
> HandleChildCrash(pid, exitstatus,
> _("WAL writer process"));
Yes, we usually use that spelling in user-facing messages.
> Personally, I prefer "wal writer", "wal sender" and "wal receiver"
> that separate words as other process names. But I don't mind leaving
> them as they are now.
If we were to change those, that would break existing queries for
pg_stat_activity. That's new in PG10, so we could change it if we were
really eager. But it's probably not worth bothering. Then again, there
is pg_stat_wal_receiver. So it's all totally inconsistent. Not sure
where to go.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2017-09-20 01:30:53 | Re: sync process names between ps and pg_stat_activity |
Previous Message | Andres Freund | 2017-09-20 01:06:29 | Re: pgsql: Make new crash restart test a bit more robust. |