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

From Andres Freund
Subject Re: Disallow setting client_min_messages > ERROR?
Date
Msg-id 20181108160630.d257akzmjhkoj7kb@alap3.anarazel.de
Whole thread Raw
In response to Re: Disallow setting client_min_messages > ERROR?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

On 2018-11-08 10:56:33 -0500, Tom Lane wrote:
> OK, so the consensus seems to be that the back branches should continue
> to allow you to set client_min_messages = FATAL/PANIC, but then ignore
> that and act as though it were ERROR.

Sounds good.


> We could implement the clamp either in elog.c or in a GUC assignment
> hook.  If we do the latter, then SHOW and pg_settings would report the
> effective value rather than what you set.  That seems a bit cleaner
> to me, and not without precedent.  As far as the backwards compatibility
> angle goes, you can invent scenarios in which either choice could be
> argued to break something; but I think the most likely avenue for
> trouble is if the visible setting doesn't match the actual behavior.
> So I'm leaning to the assign-hook approach; comments?

Seems reasonable.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Disallow setting client_min_messages > ERROR?
Next
From: "Jonah H. Harris"
Date:
Subject: Re: Disallow setting client_min_messages > ERROR?