On Thu, May 31, 2012 at 12:19 PM, Chris Angelico wrote:
> On Thu, May 31, 2012 at 2:05 PM, Evan Rempel wrote:
>> 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.
>
> The problem isn't so much
On Wed, May 30, 2012 at 09:05:23PM -0700, Evan Rempel wrote:
> I am part of a team that fills an operational roll administering 1000+
> servers and
> 100's of applications. Of course we need to "read" all of our logs, and must
> use computers to
> help us. In filtering postgreSQL logs there is on
Can this be done to syslog destination?
Evan Rempel
Systems Administrator
University of Victoria
On 2012-05-30, at 10:37 PM, "Tom Lane" wrote:
> Evan Rempel writes:
>> Even when the wrap column is set to a very large value (32k) STATEMENT lines
>> still wrap according to the line breaks in
>>
On Thu, May 31, 2012 at 2:05 PM, Evan Rempel wrote:
> 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.
The problem isn't so much the wrapping, it seems, as that your
statements' line breaks are
Evan Rempel 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
I am part of a team that fills an operational roll administering 1000+ servers
and
100's of applications. Of course we need to "read" all of our logs, and must
use computers to
help us. In filtering postgreSQL logs there is one thing that makes life
difficult for us admins.
Nice things about th
