Re: Disallow setting client_min_messages > ERROR?

Поиск
Список
Период
Сортировка
От Isaac Morland
Тема Re: Disallow setting client_min_messages > ERROR?
Дата
Msg-id CAMsGm5dX2wsJ=a-DVviK9KbZsQJ37OcQUpFDFszQNjd7VFAw=g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Disallow setting client_min_messages > ERROR?  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Ответы Re: Disallow setting client_min_messages > ERROR?  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Список pgsql-hackers
On Tue, 6 Nov 2018 at 14:07, Jonah H. Harris <jonah.harris@gmail.com> wrote:
Two options presented:

- Hard patch removes FATAL/PANIC from client_message_level_options in guc.c, which also seems to make sense in regard to it's double-usage with trace_recovery_messages.

- Soft patch keeps FATAL/PANIC in client_message_level_options but coerces client_min_messages to ERROR when set to FATAL/PANIC and issues a warning. This also exports error_severity from elog.c to retrieve severity -> text mappings for the warning message.

 
What about no-op (soft patch) for 11.1 and backpatches, error (hard patch) for 12?

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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: ATTACH/DETACH PARTITION CONCURRENTLY
Следующее
От: Andrew Gierth
Дата:
Сообщение: Re: Optimizing nested ConvertRowtypeExpr execution