Re: fix log_min_duration_statement logic error
От | Alvaro Herrera Munoz |
---|---|
Тема | Re: fix log_min_duration_statement logic error |
Дата | |
Msg-id | 20031006145102.GC5175@dcc.uchile.cl обсуждение исходный текст |
Ответ на | Re: fix log_min_duration_statement logic error (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: fix log_min_duration_statement logic error
|
Список | pgsql-patches |
On Mon, Oct 06, 2003 at 10:42:57AM -0400, Tom Lane wrote: > Bruce Momjian <pgman@candle.pha.pa.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[@]dcc.uchile.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)
В списке pgsql-patches по дате отправления: