Skip site navigation (1) Skip section navigation (2)

Re: Parsing config files in a directory

From: Cédric Villemain <cedric(dot)villemain(at)dalibo(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Greg Smith <gsmith(at)gregsmith(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Subject: Re: Parsing config files in a directory
Date: 2009-10-29 11:55:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Le dimanche 25 octobre 2009 10:08:33, Peter Eisentraut a écrit :
> 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.

Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53 -

In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2009-10-29 12:23:05
Subject: Re: Parsing config files in a directory
Previous:From: Peter EisentrautDate: 2009-10-29 11:49:53
Subject: Re: Parsing config files in a directory

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group