| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, David Johnston <polobo(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, Gregory Stark <gsstark(at)mit(dot)edu> |
| 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: | 2013-08-02 04:13:05 |
| Message-ID: | 20130802041304.GG5669@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Thu, Aug 1, 2013 at 8:27 PM, Stephen Frost <sfrost(at)snowman(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-08-02 04:20:15 | No more need for pg_clearxlogtail? |
| Previous Message | Alvaro Herrera | 2013-08-02 04:03:20 | Re: strange IS NULL behaviour |