Re: Disallow setting client_min_messages > ERROR? - Mailing list pgsql-hackers

From Isaac Morland
Subject Re: Disallow setting client_min_messages > ERROR?
Date
Msg-id CAMsGm5dX2wsJ=a-DVviK9KbZsQJ37OcQUpFDFszQNjd7VFAw=g@mail.gmail.com
Whole thread Raw
In response to Re: Disallow setting client_min_messages > ERROR?  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Responses Re: Disallow setting client_min_messages > ERROR?
List 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 by date:

Previous
From: Simon Riggs
Date:
Subject: Re: ATTACH/DETACH PARTITION CONCURRENTLY
Next
From: Andrew Gierth
Date:
Subject: Re: Optimizing nested ConvertRowtypeExpr execution