Re: [Util] Warn and Remove Invalid GUCs
| От | David G. Johnston |
|---|---|
| Тема | Re: [Util] Warn and Remove Invalid GUCs |
| Дата | |
| Msg-id | CAKFQuwbP=d-VyzLsasXdUY0O-BniAK_Detd1ChCKc0fOwNEpdQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [Util] Warn and Remove Invalid GUCs (Shaik Mohammad Mujeeb <mujeeb.sk@zohocorp.com>) |
| Список | pgsql-hackers |
On Thu, May 22, 2025 at 8:43 AM Shaik Mohammad Mujeeb <mujeeb.sk@zohocorp.com> wrote:
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 namedwarn_on_unregistered_guc_prefix), which defaults tofalse, 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?
The need for yet another GUC makes this considerably less appealing than it already is.
I see and agree with the problem statement posed here but would prefer an approach that improves the UX to minimize such mistakes or encourages people to check their settings more easily to ensure that they didn't type 100 when they meant to type 10 for the correct setting name. In short, warning in limited places for a subset of potential errors when doing so involves false positives is just an unappealing change.
David J.
В списке pgsql-hackers по дате отправления: