Re: warn if GUC set to an invalid shared library - Mailing list pgsql-hackers

From Tom Lane
Subject Re: warn if GUC set to an invalid shared library
Date
Msg-id 734432.1658518007@sss.pgh.pa.us
Whole thread Raw
In response to Re: warn if GUC set to an invalid shared library  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: warn if GUC set to an invalid shared library
List pgsql-hackers
Justin Pryzby <pryzby@telsasoft.com> writes:
> On Fri, Jul 22, 2022 at 03:00:23PM -0400, Tom Lane wrote:
>> Shouldn't you be doing this when the source is PGC_S_TEST, instead?

> That makes sense, but it doesn't work for ALTER SYSTEM, which uses PGC_S_FILE.

Hmph.  I wonder if we shouldn't change that, because it's a lie.
The value isn't actually coming from the config file, at least
not yet.

We might need to invent a separate PGC_S_TEST_FILE value; or maybe it'd
be better to pass the "this is a test" flag separately?  But that'd
require changing the signature of all GUC check hooks, so probably
it's unduly invasive.  I'm not sure whether any users of the TEST
capability need to distinguish values proposed for postgresql.auto.conf
from those proposed for pg_db_role_setting ... but I guess it's
plausible that somebody might.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: Refactoring the regression tests for more independence
Next
From: Tom Lane
Date:
Subject: Re: Refactoring the regression tests for more independence