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

From Jeff Janes
Subject Re: Non-empty default log_line_prefix
Date
Msg-id CAMkU=1wEPg7n0eP9Avjqd2HDOSbKacrs3Yxx2JBi=kppeF9g7Q@mail.gmail.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>)
List pgsql-hackers
On Sun, Oct 2, 2016 at 1:20 PM, Christoph Berg <myon@debian.org> wrote:
Re: Tom Lane 2016-09-29 <18642.1475159736@sss.pgh.pa.us>
> > Possibly the longer version could be added as an example in the
> > documentation.
>
> 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.)

I don't agree with that part.  When looking at sections of log files that people post on help forums, I've often wished people had shared milliseconds, and I've never wished they had truncated them off.  

If two messages are separated by 0.950 seconds, it can have entirely different implications than if they are separated by 0.002 seconds.

What is the cost of using %m, other than 4 (rather compressible) bytes per log entry?

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Remove "Source Code" column from \df+ ?
Next
From: Tom Lane
Date:
Subject: Re: Remove "Source Code" column from \df+ ?