Re: fix log_min_duration_statement logic error
От | Tom Lane |
---|---|
Тема | Re: fix log_min_duration_statement logic error |
Дата | |
Msg-id | 27177.1065451377@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: fix log_min_duration_statement logic error (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: fix log_min_duration_statement logic error
Re: fix log_min_duration_statement logic error |
Список | pgsql-patches |
Bruce Momjian <pgman@candle.pha.pa.us> writes: > Are those lines sent to the elog as one write() or separate ones --- do > they always appear together in the log? Currently they are sent in a single fprintf(stderr), which might or might not be good enough to ensure atomicity. We could hack this to a direct write() if you don't mind depending on fileno(stderr), but I think that'd create some portability issues on non-Unix platforms. If you're using syslog then I think all bets are off anyway. > 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. regards, tom lane
В списке pgsql-patches по дате отправления: