Re: [Util] Warn and Remove Invalid GUCs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>
Cc: Shaik Mohammad Mujeeb <mujeeb(dot)sk(at)zohocorp(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, mujeebskdev <mujeeb(dot)sk(dot)dev(at)gmail(dot)com>
Subject: Re: [Util] Warn and Remove Invalid GUCs
Date: 2025-05-22 16:45:25
Message-ID: 1535254.1747932325@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com> writes:
> Tom, the problem is when the prefix is a typo ,my bad i should have
> specified as bogus prefix instead of bogus GUC ,can you please try again
> with
> "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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-05-22 16:51:58 Re: [Util] Warn and Remove Invalid GUCs
Previous Message Florents Tselai 2025-05-22 16:38:02 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part