Re: backend type in log_line_prefix?

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

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

To: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2020-03-07T15:08: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

Attachments

v3-0001-Refactor-ps_status.c-API.patch (text/plain) patch v3-0001
v3-0002-Unify-several-ways-to-tracking-backend-type.patch (text/plain) patch v3-0002
v3-0003-Add-backend-type-to-csvlog-and-optionally-log_lin.patch (text/plain) patch v3-0003
v3-0004-Remove-am_syslogger-global-variable.patch (text/plain) patch v3-0004

Updated patch set because of conflicts.

On 2020-02-21 10:09, Peter Eisentraut wrote:
> After positive initial feedback, here is a more ambitious patch set.  In
> particular, I wanted to avoid having to specify the backend type (at
> least) twice, once for the ps display and once for this new facility.
> 
> I have added a new global variable MyBackendType that uses the existing
> BackendType enum that was previously only used by the stats collector.
> Then the ps display, the stats collector, the log_line_prefix, and other
> places can just refer to this to know "who am I".  (There are more
> places like that, for example in the autovacuum system, so patch 0004 in
> particular could be expanded in analogous ways.)

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