On 01/16/2014 07:32 AM, Christian Kruse wrote: > Hi Alvaro, > > On 16/01/14 10:21, Alvaro Herrera wrote: >> 1. it is to be read automatically by the server without need for an >> "include_dir conf.d" option in the main postgresql.conf. > > +1 > >> 4. there is no point in "disabling" it, and thus we offer no mechanism >> to do that. > > Not only there is „no point“ in disabling it, it makes this feature > nearly useless. One can't rely on it if the distro may disable > it. There are so many out there, it will never be a reliable feature > if it can be disabled.
It would make *my* life vastly easier if we could mandate things like the presence and relative directory of a conf.d. However, if Apache can't do it, we certainly can't. Ultimately, we cannot impose things on distributions which they are unwilling to support; Debian, for one, will happily fork PostgreSQL rather than accept directory assignments which don't meet their standards. Also, enough people install PostgreSQL from source or using custom packages to make for a high degree of variation anyway. That's why I was just advocating changing the *defaults*, not mandating anything. Actual directory locations and usage should be configurable by distros, packagers and users. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
