Horton

Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])

Andres Freund <andres@2ndquadrant.com>

View thread View on postgr.es
From: Andres Freund <andres@2ndquadrant.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Dimitri Fontaine <dimitri@2ndQuadrant.fr>, David Johnston <polobo@yahoo.com>, pgsql-hackers@postgresql.org, Amit Kapila <amit.kapila@huawei.com>, Gregory Stark <gsstark@mit.edu>, Stephen Frost <sfrost@snowman.net>
Date: 2013-08-01T17:24:43Z
Lists: pgsql-hackers 
On 2013-08-01 10:16:59 -0700, Josh Berkus wrote:
> Dimitri,
> 
> > We rehash because the situation did change *a lot*. We just decided that
> > the ALTER SYSTEM SET setup will live in PGDATA and will not have to be
> > edited by DBA nor sysadmin nor tools ever. We will have a separate
> > facility (conf.d) for that. As a result, I don't think there's any
> > issues left with one-setting-per-file now.
> 
> Let's please NOT call it conf.d if it's living in PGDATA and is not
> meant to be edited by hand.  conf.d is for a directory of config files
> created by users and external utilities, living in CONFIGDIR.

How nice that that's not what's being discussed here then. conf.d *IS*
the thing thats been proposed to be a separate feature from ALTER
SYSTEM. For the use case you describe.

Greetings,

Andres Freund

-- 
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services