Re: Change request - log line prefix

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Evan Rempel <erempel(at)uvic(dot)ca>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Change request - log line prefix
Date: 2012-05-31 05:06:35
Message-ID: 28335.1338440795@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chris Angelico 2012-05-31 05:19:15 Re: Change request - log line prefix
Previous Message Evan Rempel 2012-05-31 04:05:23 Change request - log line prefix

Browse pgsql-general by date

  From Date Subject
Next Message Chris Angelico 2012-05-31 05:19:15 Re: Change request - log line prefix
Previous Message savio rodriges 2012-05-31 04:25:46 Your question...