Re: Disallow setting client_min_messages > ERROR?

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Disallow setting client_min_messages > ERROR?
Date: 2018-11-06 19:07:02
Message-ID: CADUqk8V8A8b397L8LSo5eux0SN3HHUvwCoZtdSNd=4ZEzbJA6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Jonah H. Harris

Attachment Content-Type Size
client_min_messages_config_hard.patch application/octet-stream 436 bytes
client_min_messages_config_soft.patch application/octet-stream 2.8 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-11-06 19:10:51 Re: ATTACH/DETACH PARTITION CONCURRENTLY
Previous Message Robert Haas 2018-11-06 19:05:57 Re: ATTACH/DETACH PARTITION CONCURRENTLY