Re: Badly designed error reporting code in controldata_utils.c

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Badly designed error reporting code in controldata_utils.c
Дата
Msg-id CAB7nPqS95SZ2sKs14chHH44JiW3b79-XojqLXWZ0uyFTrAeBAA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Badly designed error reporting code in controldata_utils.c  (Andres Freund <andres@anarazel.de>)
Ответы Re: Badly designed error reporting code in controldata_utils.c  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
On Mon, Mar 7, 2016 at 10:26 AM, Andres Freund <andres@anarazel.de> wrote:
> FWIW I'm considering implementing elog/ereport properly for the
> frontend.  We've grown several hacks around that not being present, and
> I think those by now have a higher aggregate complexity than a proper
> implementation would have.

That would be handy. And this is are going to need something like
callbacks to allow frontend applications how to apply elevel. Take for
example pg_rewind, it has an interface with DEBUG and PROGRESS level
directly embedded with FATAL controlled by user-defined options.
-- 
Michael



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

Предыдущее
От: Haribabu Kommi
Дата:
Сообщение: Re: pam auth - add rhost item
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Badly designed error reporting code in controldata_utils.c