From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | 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-07-29 21:03:02 |
Message-ID: | 51F6D886.4080609@timbira.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 18-07-2013 17:02, Alvaro Herrera wrote:
> I think we should just put the config directives of ALTER SYSTEM into a
> file, not dir, alongside postgresql.conf; I would suggest
> postgresql.auto.conf. This file is parsed automatically after
> postgresql.conf, without requiring an "include" directive in
> postgresql.conf. If the user does not want that file, they can remove
> it; but a future ALTER SYSTEM will create the file again. No need to
> parse stuff to find out whether the directory exists, or the file
> exists, or such nonsense.
>
+1. Let's keep it as simple as possible. There will be the possibility
to revisit the directory and/or include* ideas.
> I think the only drawback of this is that there's no way to disable
> ALTER SYSTEM (i.e. there's no directory you can remove to prevent the
> thing from working).
>
Disable ALTER SYSTEM? No, thanks. Change the postgresql.auto.conf
permissions or ownership is an elegant way to disable it.
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2013-07-29 21:36:47 | Re: Add json_typeof() and json_is_*() functions. |
Previous Message | Josh Berkus | 2013-07-29 19:46:39 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |