Re: Change request - log line prefix - Mailing list pgsql-general

From Evan Rempel
Subject Re: Change request - log line prefix
Date
Msg-id E4C9ECD7-D6F9-4557-8A8F-576B7F4DC7AF@uvic.ca
Whole thread Raw
In response to Re: Change request - log line prefix  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Can this be done to syslog destination?

Evan Rempel
Systems Administrator
University of Victoria

On 2012-05-30, at 10:37 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:

> Evan Rempel <erempel@uvic.ca> writes:
>> Even when the wrap column is set to a very large value (32k) STATEMENT lines still wrap according to the line breaks
in
>> the original SQL statement.
>> Wrapped line no longer have the prefix - difficult to grep the log for everything pertaining to a particular
databaseor user 
>> Wrapped lines no longer have the log line status - difficult to auto-ignore all NOTICE status log lines when they
wrap,or 
>> ignore all user STATEMENT lines because they almost always wrap.
>
> I think your life would be better if you used CSV log format.
>
>> In conclusion, I would like to see a logging change that included the prefix on EVERY line, and included the STATUS
onevery line. 
>
> This doesn't really sound like an improvement to me.  It's going to make
> the logs bulkier, but they're still not automatically parseable in any
> meaningful sense.  CSV is the way to go if you want machine-readable logs.
>
>            regards, tom lane

pgsql-general by date:

Previous
From: Chris Angelico
Date:
Subject: Re: Change request - log line prefix
Next
From: "Bart Lateur"
Date:
Subject: Re: Postgres no longer starts