| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | 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>, Stephen Frost <sfrost(at)snowman(dot)net> |
| 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-01 17:16:59 |
| Message-ID: | 51FA980B.9030603@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dimitri,
> We rehash because the situation did change *a lot*. We just decided that
> the ALTER SYSTEM SET setup will live in PGDATA and will not have to be
> edited by DBA nor sysadmin nor tools ever. We will have a separate
> facility (conf.d) for that. As a result, I don't think there's any
> issues left with one-setting-per-file now.
Let's please NOT call it conf.d if it's living in PGDATA and is not
meant to be edited by hand. conf.d is for a directory of config files
created by users and external utilities, living in CONFIGDIR.
If we're going to have a directory of individual file settings in
PGDATA, let's be consistent with the existing command and call it
"system_set".
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-08-01 17:21:14 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
| Previous Message | Josh Berkus | 2013-08-01 17:13:37 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |