From: | Alvaro Herrera Munoz <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 14:51:02 |
Message-ID: | 20031006145102.GC5175@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Mon, Oct 06, 2003 at 10:42:57AM -0400, Tom Lane wrote:
> 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,
>
> That's a thought... seems less invasive than the backslashing. Not sure
> how well it'll work for syslog output though.
Not good. Some syslogs will replace the literal tab with a ^I.
Maybe it should be a bunch of spaces when using syslog.
It seems a good idea to me anyway.
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
?
--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"Find a bug in a program, and fix it, and the program will work today.
Show the program how to find and fix a bug, and the program
will work forever" (Oliver Silfridge)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-10-06 15:08:10 | pg_restore -d doesn't display output |
Previous Message | Tom Lane | 2003-10-06 14:42:57 | Re: fix log_min_duration_statement logic error |