To: Evan Rempel <erempel@uvic.ca>
cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: Change request - log line prefix 
In-reply-to: <F1226B1821911E4BB69462DAF68098536E32333755@EMC6.uvic.ca> 
References: <4F8B6AA1.1040709@zvelo.com>
	<20120416065717.70a31a6361ac5d7bdad416e8@frank.uvena.de>
	<4F8BD91C.6070405@zvelo.com> <4F8BDAB2.7010209@frank.uvena.de>
	<4F8C248E.7070307@zvelo.com> <4F8CC11A.5020003@d2.com>
	<4F8CDB95.3040407@zvelo.com>
	<A76B25F2823E954C9E45E32FA49D70EC03DACFB6@mail.corp.perceptron.com>,
	<4F8E04D9.6010402@zvelo.com>
	<F1226B1821911E4BB69462DAF68098536E32333755@EMC6.uvic.ca>
Comments: In-reply-to Evan Rempel <erempel@uvic.ca>
	message dated "Wed, 30 May 2012 21:05:23 -0700"
Date: Thu, 31 May 2012 01:06:35 -0400
Message-ID: <28335.1338440795@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

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 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