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

From Robert Haas
Subject Re: Non-empty default log_line_prefix
Date
Msg-id CA+TgmoaJBFCmz9669pxuryoOoG=y=YhLVGHRXr6NLYpG-pQ8OA@mail.gmail.com
Whole thread Raw
In response to Re: Non-empty default log_line_prefix  (Christoph Berg <myon@debian.org>)
Responses Re: Non-empty default log_line_prefix  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Wed, Oct 12, 2016 at 11:20 AM, Christoph Berg <myon@debian.org> wrote:
> Re: Jeff Janes 2016-10-12 <CAMkU=1zmOp5T70MX508nwFf8tvv2jOT+hGwLq8fNHLSxp-wVmQ@mail.gmail.com>
>> Do you think the pushback will come from people who just accept the
>> defaults?
>
> I'm concerned about readability. "2016-10-12 20:14:30.449 CEST" is a
> lot of digits. My eyes can parse "20:14:30" as a timestamp, but
> "20:14:30.449" looks more like an IP address. (Admittedly I don't have
> experience with reading %m logs.)
>
> Overall, I'd prefer %t but %m would be ok as well.

I'm fine with either!  Both are much better than the empty string.
One of the problems with the status quo is that many users don't even
realize that log_line_prefix exists, so they don't configure it at
all.  They don't even realize that they have the option to add a
prefix.  I think configuring a non-empty default will be both better
by default and more likely to make people realize that they have
choices.

-- 
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: pg_dump getBlobs query broken for 7.3 servers