| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Cédric Villemain <cedric(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, 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> |
| Subject: | Re: Disabling ALTER SYSTEM SET WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters |
| Date: | 2013-08-06 18:53:47 |
| Message-ID: | 20130806185347.GB10718@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus escribió:
> (2) Enabling DBAAS services to give users limited control over settings.
> (5) Enabling new ways of writing Puppet/Chef/etc. scripts, which can
> check a setting before changing it.
Surely these two cases are better covered by conf.d. For (2), DBaaS
providers could offer pre-cooked snippets that are dropped in conf.d at
the click of a button. For (5) it should be obvious that conf.d is
better than ALTER SYSTEM.
Not clear on (4); I think conf.d would also solve that one.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2013-08-06 18:55:46 | Re: Disabling ALTER SYSTEM SET WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters |
| Previous Message | Robert Haas | 2013-08-06 18:51:22 | Re: latest pgbench results |