> On Jul 31, 2018, at 10:59 AM, Dimitri Maziuk <dmaziuk@xxxxxxxxxxxxx> wrote: > > On 07/31/2018 12:33 PM, George Neuner wrote: > >> Is there some reason that postgresql.conf cannot be a link to your >> file? > > It's six of one, half a dozen of the other. The big problem is when the > network share is unavailable at host boot and all of your databases are > belong to bitbucket. If you want to do it right, you need chef/puppet as > already suggested. > > One useful thing linux (at least) has now is conf.d directories whose > contents are auto-included after the main config: this way you can keep > the vendor-provided /etc/blah.conf and have all your host-specific > settings in /etc/blah.d/myhost.conf, all living together happily ever > after. You still want the latter to be a local file that's guaranteed > available when blah service starts up. (Postgres devs: hint! hint!) You'd do that with "include_dir 'conf.d'" or similar, I think, which PostgreSQL has in all current versions. Cheers, Steve
