Search Postgresql Archives

Re: Change request - log line prefix

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxx> wrote:

> Evan Rempel <erempel@xxxxxxx> 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

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux