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])

Stephen Frost <sfrost@snowman.net>

View thread View on postgr.es
From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Andres Freund <andres@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>, 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>
Date: 2013-08-01T18:37:45Z
Lists: pgsql-hackers 
* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> Andres Freund wrote:
> 
> > Postgresql.auto.conf.d is what I'd propose, but the decision about
> > that seems to be one of the smaller problems around this feature...
> > That naming seems to make it sensible to extend other files (hba,
> > ident) similarly at a later point.
> 
> I don't like this particular naming proposal, but I'm glad this patch
> finally seems to be getting somewhere.

Yeah, also not a fan.  We don't have any 'conf.d' directories in PGDATA
and I don't think we should start now.  I liked Josh's suggestions of
something like "system_conf".  For multiple independent config files, we
could use directories under that (eg: 'pgconf', 'pghba', 'pgident'..).

	Thanks,

		Stephen