Horton

Re: backend type in log_line_prefix?

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: fabriziomello@gmail.com, alvherre@2ndquadrant.com, pgsql-hackers@postgresql.org
Date: 2020-04-01T13:44:01Z
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 →

  1. Add backend type to csvlog and optionally log_line_prefix

  2. Remove am_syslogger global variable

  3. Unify several ways to tracking backend type

  4. Refactor ps_status.c API

  5. Add background worker type

On 2020-04-01 03:55, Bruce Momjian wrote:
> Agreed.  I ended up moving "wal" as a separate word, since it looks
> cleaner;  patch attached.  Tools that look for the backend type in
> pg_stat_activity would need to be adjusted;  it would be an
> incompatibility.  Maybe changing it would cause too much disruption.

Yeah, it's probably not worth the change for that reason.  There is no 
confusion what the "archiver" is.  Also, we have archive_mode, 
archive_command, etc. without a wal_ prefix.  Let's leave it as is.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services