Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Josh Berkus <josh@agliodbs.com>, Amit Kapila <amit.kapila@huawei.com>, "'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>, "'Dimitri Fontaine'" <dimitri@2ndquadrant.fr>, pgsql-hackers@postgresql.org
Date: 2013-08-02T19:23:29Z
Lists: pgsql-hackers 
Stephen Frost <sfrost@snowman.net> writes:
> * Josh Berkus (josh@agliodbs.com) wrote:
>> A much simpler solution to the issue Stephen proposes is to have a way
>> to start up the server with all settings from ALTER SYSTEM SET disabled,
>> just like some software allows you to start it up in "safe mode".

> See above for why I'm not thrilled wih this approach, unless it was set
> up to happen automatically, but you couldn't simply ignore *all* the
> ALTER SYSTEM SET parameters because then you might not be able to
> connect in due to some ALTER SYSTEM SET parameter being necessary for
> remote connectivity or authentication.

Yeah, this approach is a nonstarter because there's no reason to assume
that a postmaster started with default parameters will start successfully,
or will be connectable-to if it does start.  Maybe there's another
postmaster hogging the default port, for instance.

			regards, tom lane