From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Rod Taylor <rbt(at)rbt(dot)ca>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: fix log_min_duration_statement logic error |
Date: | 2003-10-06 15:17:30 |
Message-ID: | 27419.1065453450@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl> writes:
>> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> I had a new idea on output format. Instead of converting newline to
>> "\n", and double-escaping backslashes, we add a tab after any newline,
> Not good. Some syslogs will replace the literal tab with a ^I.
That seems okay. We just want to make sure continuation lines are
easily distinguishable. (But leading spaces would be okay with me too.)
> How would it handle multiple fields? Say
> LOG: blah blah
> DETAIL: something
> HINT: something else
> Will it be
> LOG: blah blah
> DETAIL: something else
> HINT: something else
No, one would hope no tab before DETAIL/HINT/etc. The idea is to be
able to recognize when the contents of one of these entries spans lines.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira de Oliveira | 2003-10-06 15:30:39 | brazilian portuguese translations |
Previous Message | Bruce Momjian | 2003-10-06 15:08:10 | pg_restore -d doesn't display output |