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

From Tom Lane
Subject Re: Change request - log line prefix
Date
Msg-id 28335.1338440795@sss.pgh.pa.us
Whole thread Raw
In response to Change request - log line prefix  (Evan Rempel <erempel@uvic.ca>)
Responses Re: Change request - log line prefix
List pgsql-general
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 database
oruser 
> 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: savio rodriges
Date:
Subject: Your question...
Next
From: Chris Angelico
Date:
Subject: Re: Change request - log line prefix