Re: proposal: a validator for configuration files

Pavel Stehule <pavel.stehule@gmail.com>

From: Pavel Stehule <pavel.stehule@gmail.com>

To: Florian Pflug <fgp@phlo.org>

Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@commandprompt.com>, Alexey Kluykin <alexk@commandprompt.com>, Selena Deckelmann <selena@chesnok.com>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2011-07-18T03:30:48Z

Lists: pgsql-hackers

2011/7/18 Florian Pflug <fgp@phlo.org>:
> On Jul18, 2011, at 01:29 , Robert Haas wrote:
>> Hmm.  Maybe what we need is a mechanism that allows the configuration
>> to be associated a loadable module, and whenever that module is
>> loaded, we also load the associated configuration settings.  This is
>> probably terribly syntax, but something like:
>>
>> ALTER LOAD 'plpgsql' SET plpgsql.variable_conflict = 'whatever';
>
> A variant of this would be to allow extensions (in the CREATE EXTENSION
> sense) to declare custom GUCs in their control file. Then we'd only
> need to load those files, which seems better than loading a shared
> library.

+1

Pavel

>
> We do expect people to wrap their loadable modules in extensions
> anyway nowadays, do we?
>
> best regards,
> Florian Pflug
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>