Re: Disallow setting client_min_messages > ERROR?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jonah H. Harris" <jonah.harris@gmail.com>
Cc: andres@anarazel.de,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-11-08T22:37:06Z
Lists: pgsql-hackers
"Jonah H. Harris" <jonah.harris@gmail.com> writes: > On Thu, Nov 8, 2018 at 10:56 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> 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? > My patch used the check hook, but works either way. I was deliberately not getting into the detail of which hook to use ;-). Anyway, pushed with some adjustments and work on the documentation. Notably, I thought the warning message was inappropriate and overcomplicated, so I just dropped it. I don't think we really need anything there. regards, tom lane
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