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

From Alvaro Herrera
Subject Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Date
Msg-id 20130802041304.GG5669@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
> On Thu, Aug 1, 2013 at 8:27 PM, Stephen Frost <sfrost@snowman.net> wrote:
> > The point above is that we will always need some amount of external
> > config file and, as such, we should probably consider which items should
> > really only be set in the *config* files and which can be set in either
> > place.

I think this idea might make some sense: mark the settings (add a
flag bit in the guc.c tables) that can be changed via alter setting.  Or
perhaps add the bit to ones that can *not* be changed.

I don't think we need to promise exact compatibility on the set of
settings that can be changed via ALTER SYSTEM.  If you can change
setting XYZ in 9.4, and we find that it wasn't such a good idea and
have to disallow it in 9.5, well, too bad.  (Or perhaps even a minor
version.  Am I sacrilegious?)

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: strange IS NULL behaviour
Next
From: Bruce Momjian
Date:
Subject: No more need for pg_clearxlogtail?