Horton

Re: File-per-GUC WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])

Bruce Momjian <bruce@momjian.us>

View thread View on postgr.es
From: Bruce Momjian <bruce@momjian.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Josh Berkus <josh@agliodbs.com>, Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@2ndquadrant.com>, Greg Stark <stark@mit.edu>, Alvaro Herrera <alvherre@2ndquadrant.com>, Fujii Masao <masao.fujii@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Amit Kapila <amit.kapila@huawei.com>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, pgsql-hackers@postgresql.org
Date: 2013-08-05T18:04:42Z
Lists: pgsql-hackers 
On Mon, Aug  5, 2013 at 02:02:50PM -0400, Stephen Frost wrote:
> * Josh Berkus (josh@agliodbs.com) wrote:
> > I'll also point out that some of our settings only really "work" in
> > combinations of two or more settings.  For example, one doesn't want to
> > set archive_mode = on unless one is setting archive_command as well.
> 
> And one doesn't want to set archive_command w/o doing some kind of setup
> work on the server in question, perhaps setting up SSH keys or putting a
> decent shell script in place to be called from archive_command.  That's
> part of my issue w/ this- the parameters which can't be set up correctly
> through sole use of "ALTER SYSTEM" should be excluded from it and
> instead set up through a config file.

Yes, but many setting changes don't require file system changes.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +