Re: Parsing config files in a directory - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Parsing config files in a directory
Date
Msg-id 1256461713.9848.2.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Parsing config files in a directory  (Greg Smith <gsmith@gregsmith.com>)
Responses Re: Parsing config files in a directory
Re: Parsing config files in a directory
Re: Parsing config files in a directory
List pgsql-hackers
On lör, 2009-10-24 at 13:32 -0400, Greg Smith wrote:
> Regardless, the UI I was hoping for was to make the default 
> postgresql.conf file end with a line like this:
> 
> directory 'conf'

I think something like is this is definitely more understandable for
users and less overkill in the implementation.

As a file point, I would prefer something like

include 'whatever/*.conf'

that is, listing the files as a glob pattern instead of naming a
directory.  Because packaging tools, editors, etc. will leave backup and
temporary files lying around that you don't want to include, and we
don't want to get involved into knowing all the naming patterns that
people might want to use for those.

Actually,

include 'postgresql.conf.d/*.conf'

sounds nice as a default.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Parsing config files in a directory
Next
From: Guillaume Smet
Date:
Subject: Re: Parsing config files in a directory