On Tue, Aug 20, 2013 at 7:51 PM, Stephen Frost <sfr...@snowman.net> wrote:
> * Amit Kapila (amit.kapil...@gmail.com) wrote:
>> Wouldn't it be complicated to handle this way rather then by having
>> include directive.
>
> You misunderstood. I was suggesting a setup along these lines:
>
> postgresql.conf:
> # include = 'auto.conf' # Disabled by default
>
> auto.conf:
> ####################################################
> # MANAGED BY ALTER SYSTEM -- DO NOT MODIFY BY HAND
> ####################################################
>
> # auto.conf not processed unless included by postgresql.conf
> # If included by postgresql.conf, then this will turn on the
> # ALTER SYSTEM command.
> enable_alter_system = on
>
> Which would give us the ability to independently turn on/off ALTER
> SYSTEM from including auto.conf.
So let me try to explain what I understood from above:
1. enable_alter_system a new GUC whose default value =off.
2. Alter System will check this variable and return error (not
allowed), if this parameter is off.
3. Now if user enables include directive in postgresql.conf, it will
enable Alter System as value of
enable_alter_system is on.
4. User can run Alter System command to disable Alter System
"enable_alter_system = off".
Now even though include directive is enabled, but new Alter System
commands will not work, however
existing parameter's take into effect on restart/sighup.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
