Re: backend type in log_line_prefix? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: backend type in log_line_prefix?
Date
Msg-id 6453e044-041a-bf64-c76a-e1b7e3d5b0e7@2ndquadrant.com
Whole thread Raw
In response to backend type in log_line_prefix?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: backend type in log_line_prefix?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: backend type in log_line_prefix?  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On 2020-02-13 09:56, Peter Eisentraut wrote:
> Attached is a demo patch that adds a placeholder %b for log_line_prefix
> (not in the default setting) that contains the backend type, the same
> that you see in pg_stat_activity and in the ps status.  I would have
> found this occasionally useful when analyzing logs, especially if you
> have a lot of background workers active.  Thoughts?

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

Attachment

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: Portal->commandTag as an enum
Next
From: Etsuro Fujita
Date:
Subject: Re: Minor improvement to partition_bounds_copy()