Re: backend type in log_line_prefix?

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>

To: bruce@momjian.us

Cc: fabriziomello@gmail.com, peter.eisentraut@2ndquadrant.com, alvherre@2ndquadrant.com, pgsql-hackers@postgresql.org

Date: 2020-03-27T07:30:07Z

Lists: pgsql-hackers

Commits

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

Add backend type to csvlog and optionally log_line_prefix
- 70a7b4776be4 13.0 landed
Remove am_syslogger global variable
- d90bd24391fd 13.0 landed
Unify several ways to tracking backend type
- 8e8a0becb335 13.0 landed
Refactor ps_status.c API
- bf68b79e50e3 13.0 landed
Add background worker type
- 5373bc2a0867 11.0 cited

Hello.

At Mon, 23 Mar 2020 18:38:53 -0400, Bruce Momjian <bruce@momjian.us> wrote in 
> Patch applied to master, thanks.

The patch (8e8a0becb3) named archiver process as just "archiver".  On
the other hand the discussion in the thread [1] was going to name the
process as "WAL/wal archiver".  As all other processes related to WAL
are named as walreceiver, walsender, walwriter, wouldn't we name the
process like "wal archiver"?

[1]: https://www.postgresql.org/message-id/20200319195410.icib45bbgjwqb5zn@alap3.anarazel.de

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center