Re: Disallow setting client_min_messages > ERROR?
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2018-11-08T16:06:30Z
Lists: 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
Commits
-
Disallow setting client_min_messages higher than ERROR.
- c09daa910409 10.7 landed
- 7b08b4a8adbb 11.2 landed
- 3d360e20c9ae 12.0 landed
- 88275ac19900 9.5.16 landed
- 2407d4807fdc 9.4.21 landed
- 041ad9a66d28 9.6.12 landed