Re: Unified logging system for command-line programs

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Unified logging system for command-line programs
Дата
Msg-id 4159.1546553023@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Unified logging system for command-line programs  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: Unified logging system for command-line programs  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 03/01/2019 22:01, Tom Lane wrote:
>> while ereport(ERROR) has the
>> effect of writing a message and then calling exit(1).

> The problem is that in majority of cases the FRONTEND code, as it is
> written today, doesn't want to exit() after an error.

Right, so for that you'd use ereport(WARNING) or LOG or whatever.

We'd probably need a bit of care about which ereport levels produce
exactly what output, but I don't think that's insurmountable.  We
do not need all the backend-side message levels to exist for frontend.

            regards, tom lane


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

Предыдущее
От: David Rowley
Дата:
Сообщение: Re: Delay locking partitions during query execution
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Unified logging system for command-line programs