Re: Configuration Parameter/GUC value validation hook - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Configuration Parameter/GUC value validation hook
Date
Msg-id 2157142.1651592741@sss.pgh.pa.us
Whole thread Raw
In response to Re: Configuration Parameter/GUC value validation hook  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Configuration Parameter/GUC value validation hook  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> I have some desire here to see us solve this problem not just for
> service providers, but for users in general. You don't have to be a
> service provider to want to disallow SET work_mem = '1TB' -- you just
> need to be a DBA on a system where such a setting will cause bad
> things to happen. But, if you are a DBA on some random system, you
> won't likely find a hook to be a particularly useful way of
> controlling this sort of thing.

Yeah, I think this is a more realistic point.  I too am not sure what
a good facility would look like.  I guess an argument in favor of
providing a hook is that we could then leave it to extension authors
to try to devise a facility that's useful to end users, rather than
having to write an in-core feature.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Erik Rijkers
Date:
Subject: SQL/JSON: FOR ORDINALITY bug
Next
From: Jacob Champion
Date:
Subject: [PATCH] Log details for client certificate failures