Re: [Util] Warn and Remove Invalid GUCs - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: [Util] Warn and Remove Invalid GUCs
Date
Msg-id CAKAnmmJ5ofEX6u82m42iRm__Q0wqcCu1TPC9zF_shwWPNpp70A@mail.gmail.com
Whole thread Raw
In response to Re: [Util] Warn and Remove Invalid GUCs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [Util] Warn and Remove Invalid GUCs
List pgsql-hackers
On Thu, May 22, 2025 at 12:45 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "lpgsql.bogus = 1" .

[ shrug... ] 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.

Well, we do have ways to view all *potential* extensions. I find myself more sympathetic to the OP than the others here, as I think it's a good idea to display a warning for a potentially misspelled GUC prefix (but do nothing else - certainly not remove it!). Will such a warning be seen? Perhaps not, but that's a risk any warning message has to face. And obviously there could be false positives if an extension decides to name their GUCs something other than pg_available_extensions()->name but hopefully that's a rare case (and shame on them if so.)

Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Assert("vacrel->eager_scan_remaining_successes > 0")
Next
From: Melanie Plageman
Date:
Subject: Re: Log connection establishment timings