Re: Change request - log line prefix

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(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Evan Rempel <erempel(at)uvic(dot)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 or 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 on every 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