Re: Custom GUCs and typos - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Custom GUCs and typos
Date
Msg-id CAKFQuwYcuyrfZXqz44N7Su8UotLcpdYc7S40D=iyi8R2xeBSAg@mail.gmail.com
Whole thread Raw
In response to Custom GUCs and typos  (Srinath Reddy Sadipiralla <srinath2133@gmail.com>)
List pgsql-hackers
On Sun, May 25, 2025 at 7:52 PM Srinath Reddy Sadipiralla <srinath2133@gmail.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.


"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.

pgsql-hackers by date:

Previous
From: Yugo Nagata
Date:
Subject: JIT works only partially with meson build?
Next
From: Tender Wang
Date:
Subject: Re: MERGE issues around inheritance