| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
| Cc: | cedric(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, 'Andres Freund' <andres(at)2ndquadrant(dot)com>, 'Alvaro Herrera' <alvherre(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>, '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 11:52:52 |
| Message-ID: | 20130802115252.GZ2706@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Amit Kapila (amit(dot)kapila(at)huawei(dot)com) wrote:
> Yes, this can be viable option to ignore variable values that don't allow
> server to start, also I agree with you that
> this can be a separate patch.
I disagree that this can be a separate patch. Adding an option to not
allow certain GUCs from being modified through this mechanism should be
trivial. Then, *after* we have such utility that will allow users to
fix a bad situation, we can consider relaxing those restrictions to
allow more values to be set. I still contend that there will be some
GUCs that simply don't make any sense to have in the auto-conf area of
PGDATA.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-08-02 12:08:14 | Re: inconsistent state after crash recovery |
| Previous Message | Stephen Frost | 2013-08-02 11:49:14 | Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |