From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila(at)huawei(dot)com>, '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>, 'Dimitri Fontaine' <dimitri(at)2ndquadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org, 'Josh Berkus' <josh(at)agliodbs(dot)com> |
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 17:34:58 |
Message-ID: | 20130802173458.GO5669@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost escribió:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> > What if you set a combination of parameters that prevents Postgres from
> > starting?
>
> This was what I was trying to get at up-thread. Things that prevent PG
> from being able to start (or, really, which cause PG to be started in a
> completely different mode, ala recovery.conf) need to be able to be
> modified outside of PG and therefore should, imv, be considered
> configuration parameters and therefore live outside of $PGDATA (when
> installed from a distro, blah, blah).
I think the way out of this situation is to have a postmaster and/or
pg_ctl switch that disables reading of ALTER SYSTEM settings. Then the
DBA can do ALTER SYSTEM RESET until it works again. No need to mess
with "data" files.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-08-02 17:49:35 | Re: CREATE MATERIALIZED VIEW .. FOR UPDATE |
Previous Message | Alvaro Herrera | 2013-08-02 16:46:33 | CREATE MATERIALIZED VIEW .. FOR UPDATE |