Re: Disallow setting client_min_messages > ERROR?

From: Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
To: jonah(dot)harris(at)gmail(dot)com
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Disallow setting client_min_messages > ERROR?
Date: 2018-11-06 19:46:28
Message-ID: CAMsGm5dX2wsJ=a-DVviK9KbZsQJ37OcQUpFDFszQNjd7VFAw=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 6 Nov 2018 at 14:07, Jonah H. Harris <jonah(dot)harris(at)gmail(dot)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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-11-06 19:49:44 Re: backend crash on DELETE, reproducible locally
Previous Message Alvaro Herrera 2018-11-06 19:45:53 Re: backend crash on DELETE, reproducible locally