Hi David J, > Because any such setting name is perfectly valid (it serves as a placeholder) > and whether it is a typo or just some valid unregistered prefix is not > something the system can know.
In my patch, I currently warn and remove invalid GUCs from the hashtable. However, as you rightly pointed out, some of these could belong to valid but unregistered prefixes. In such cases, it might not be ideal to remove them outright. Instead, it could be more helpful to simply warn the user - covering both potential typos and GUCs with valid yet unregistered prefixes. I do understand that not everyone may prefer seeing such warnings during PG server restart. To address this, we could introduce a new GUC (perhaps named warn_on_unregistered_guc_prefix), which defaults to false, preserving the existing behaviour. If explicitly enabled, it would emit warnings for these cases, giving users the choice to opt in to this feedback. Thoughts on this approach? Thanks & Regards, Shaik Mohammad Mujeeb Member Technical Staff Zoho Corp ---- On Thu, 22 May 2025 02:01:25 +0530 David G. Johnston <david.g.johns...@gmail.com> wrote --- On Wednesday, May 21, 2025, Shaik Mohammad Mujeeb <mailto:mujeeb...@zohocorp.com> wrote: Currently, if there's a typo in an extension name while adding a GUC to postgresql.conf, PostgreSQL server starts up silently without any warning. Because any such setting name is perfectly valid (it serves as a placeholder) and whether it is a typo or just some valid unregistered prefix is not something the system can know. David J.
