From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
---|---|
To: | Chris Angelico <rosuav(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Change request - log line prefix |
Date: | 2012-05-31 13:54:43 |
Message-ID: | CADmi=6MxWPkPcEdUHNZp+S2P_5Z5_hsNbWS6D+zbRd==Vt9rvA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Thu, May 31, 2012 at 12:19 PM, Chris Angelico <rosuav(at)gmail(dot)com> wrote:
> On Thu, May 31, 2012 at 2:05 PM, Evan Rempel <erempel(at)uvic(dot)ca> 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 being propagated through. So as a possible
> alternative solution, perhaps there could be an option to replace
> newlines with spaces before the line goes to the log?
I'd certainly like to see this or similar (encode the querys into a
single line of ascii, lossy is ok). I like my logs both readable and
greppable.
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2012-06-02 15:11:34 | Re: Data split -- Creating a copy of database without outage |
Previous Message | hubert depesz lubaczewski | 2012-05-31 09:37:28 | Re: Change request - log line prefix |
From | Date | Subject | |
---|---|---|---|
Next Message | John Townsend | 2012-05-31 14:36:13 | Procedural Languages |
Previous Message | Adrian Klaver | 2012-05-31 13:53:26 | Re: Postgres no longer starts |