Re: Custom GUCs and typos

On Sun, May 25, 2025 at 7:52 PM Srinath Reddy Sadipiralla <
srinath2133(at)gmail(dot)com> wrote:

> 1) On top of OP's patch I added support to warn if the prefix of custom
> GUC is invalid,for valid questions such as "How do you know that's a bogus
> prefix? It could perfectly well be a fully valid setting for an extension
> that the installation doesn't choose to preload.",we can get the info of
> such extensions using extension_file_exists() which tells that its
> installed but not preloaded thanks to Greg for proposing this,which tells
> this could be a potential valid extension ,so if its not it in
> reserved_class_prefix and also not in prefix/share/extension dir then the
> prefix is for sure invalid,so i warn and remove the GUC from hashtable.
>

People can and do create GUCs without any intention or need to write C code
or place files onto the server to make use of them.

https://www.postgresql.org/docs/current/runtime-config-custom.html

"PostgreSQL will accept a setting for any two-part parameter name."

We cannot change this. So, please include discussion of their existence in
any description of changes you wish to make in this area.

David J.