Re: Set log_line_prefix and application name in test drivers - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Set log_line_prefix and application name in test drivers
Date
Msg-id CA+Tgmoap=HvEio6Fg6__F6=YsCU-ykadx0EoMfvkeF0TBnVjvw@mail.gmail.com
Whole thread Raw
In response to Re: Set log_line_prefix and application name in test drivers  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Set log_line_prefix and application name in test drivers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Sep 28, 2016 at 10:30 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 9/28/16 6:13 PM, Robert Haas wrote:
>> Christoph/Debian:
>>     log_line_prefix = '%t [%p-%l] %q%u@%d '
>> Peter:
>>     log_line_prefix = '%t [%p]: [%l] %qapp=%a '
>
> I'm aware of two existing guidelines on log line formats: syslog and
> pgbadger.  Syslog output looks like this:
>
> Sep 28 00:58:56 hostname syslogd[46]: some text here
>
> pgbadger by default asks for this:
>
> log_line_prefix = '%t [%p]: [%l-1] user=%u,db=%d,app=%a,client=%h '
>
> I don't know why it wants that "-1" there, and I'm actually not sure
> what the point of %l is in practice.  Those are separate issues that are
> having their own lively discussions at times.  I could drop the [%l]
> from my proposal if that causes concerns.
>
> On balance, I think my proposal is more in line with existing
> wide-spread conventions.

As long as we get %t and %p in there we're going to be way ahead, really.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Speed up Clog Access by increasing CLOG buffers
Next
From: Robert Haas
Date:
Subject: Re: Tuplesort merge pre-reading