Re: Non-empty default log_line_prefix - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Non-empty default log_line_prefix
Date
Msg-id 0caa6d7f-deb6-9a43-2b38-60e63af93183@2ndquadrant.com
Whole thread Raw
In response to Non-empty default log_line_prefix  (Christoph Berg <myon@debian.org>)
Responses Re: Non-empty default log_line_prefix  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Non-empty default log_line_prefix  (Christoph Berg <myon@debian.org>)
List pgsql-hackers
On 10/2/16 4:20 PM, Christoph Berg wrote:
>> I suspect that simply having a nonempty default in the first place
>> > is going to do more to raise peoples' awareness than anything we
>> > could do in the documentation.  But perhaps an example along these
>> > lines would be useful for showing proper use of %q.
> Patch attached. (Still using %t, I don't think %m makes sense for the
> default.)

That still doesn't address what to do about syslog and eventlog users.
We would need either a separate prefix setting for those, or maybe
something like %q that says, skip to here if using syslog.  (I don't
know eventlog, so I don't know if a common setting for syslog and
eventlog would work.)

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits.
Next
From: Tom Lane
Date:
Subject: Re: Renaming of pg_xlog and pg_clog