[Util] Warn and Remove Invalid GUCs

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Shaik Mohammad Mujeeb <mujeeb(dot)sk(at)zohocorp(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, mujeebskdev <mujeeb(dot)sk(dot)dev(at)gmail(dot)com>
Subject: [Util] Warn and Remove Invalid GUCs
Date: 2025-05-21 20:31:25
Message-ID: CAKFQuwbuqLNafkPuOZHzEHef3rxf8Uu9YGhL=31BOJjTUEn8+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, May 21, 2025, Shaik Mohammad Mujeeb <mujeeb(dot)sk(at)zohocorp(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-05-21 20:38:58 Re: [Util] Warn and Remove Invalid GUCs
Previous Message Tom Lane 2025-05-21 20:20:17 Re: [PATCH] Add pretty-printed XML output option