| From: | Dimitri Maziuk <dmaziuk(at)bmrb(dot)wisc(dot)edu> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Question on postgresql.conf |
| Date: | 2018-07-31 17:59:03 |
| Message-ID: | e3a71331-3113-34d2-6bde-fe663293abb8@bmrb.wisc.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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!)
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2018-07-31 18:05:47 | Re: Question on postgresql.conf |
| Previous Message | George Neuner | 2018-07-31 17:33:50 | Re: Question on postgresql.conf |