Re: WIP patch - INSERT-able log statements

Поиск
Список
Период
Сортировка
От Guillaume Smet
Тема Re: WIP patch - INSERT-able log statements
Дата
Msg-id 1d4e0c10702190821q3bb81b0fv52fb11b2b448c84a@mail.gmail.com
обсуждение исходный текст
Ответ на Re: WIP patch - INSERT-able log statements  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: WIP patch - INSERT-able log statements  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: WIP patch - INSERT-able log statements  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-patches
On 2/19/07, Alvaro Herrera <alvherre@commandprompt.com> wrote:
> I don't think the syslog option is so nice to use these days; the
> redirect_stderr stuff is more powerful and easy to use.

Did you already analyze logs of a highly loaded platform using stderr?
It's impossible to guarantee the consistency of the queries because
you can have:
Query 1 Line 1
Query 2 Line 1
Query 3 Line 1
Query 1 Line 2
Query 2 Line 2
Query 1 Line 3
Query 3 Line 2
(each query is run on a different backend). With stderr you don't have
sufficient information to know the query you should append the text
to. Syslog adds useful context information (pid, command line, command
number) which allows you to guarantee the consistency.
It's a real problem for us and that's why I don't recommend using
stderr when you use pgFouine.
Moreover, syslog can send the log to the network which moves the I/O
needed to log on another box and it's necessary in our case.

--
Guillaume

В списке pgsql-patches по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: further bootstrap cleanup
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: WIP patch - INSERT-able log statements