From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Greg Stark <stark(at)mit(dot)edu>, Andres Freund <andres(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-05 16:41:52 |
Message-ID: | 51FFD5D0.1090205@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
All,
To limit the argument here, let's please not argue about things which
people already agree on. So:
We seem to have consensus around:
A) the inadvisability of storing GUCs in a system catalog.
B) the utility of a conf.d in /etc/ which may have nothing to do with
ALTER SYSTEM SET
C) that any file for ALTER SYSTEM SET go in $PGDATA somewhere.
What we are still arguing about:
D) one-big-file vs. file-per-setting
E) whether "unsafe" settings or "restart" settings should be allowed in
ALTER SYSTEM SET.
F) whether admins need the ability to disable ALTER SYSTEM SET.
Since each of D, E and F issues are completely orthagonal to each other,
I suggest that maybe we argue them each out on their own threads? I'll
start.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-08-05 16:42:26 | Re: CREATE EVENT TRIGGER syntax |
Previous Message | Andres Freund | 2013-08-05 16:40:37 | Re: StrategyGetBuffer optimization, take 2 |