| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: could not stat promote trigger file leads to shutdown |
| Date: | 2019-11-17 01:59:01 |
| Message-ID: | 20191117015901.GA23782@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Nov-15, Tom Lane wrote:
> If we add a GUC-check-hook test, then the problem of misconfiguration
> is reduced to the previously unsolved problem that we have crappy
> feedback for erroneous on-the-fly configuration changes. So it's
> still unsolved, but at least we've got one unsolved problem not two.
I am now against this kind of behavior, because nowadays it is common
to have external orchestrating systems stopping and starting postmaster
on their own volition.
If this kind of misconfiguration causes postmaster refuse to start, it
can effectively become a service-shutdown scenario which requires the
DBA to go temporarily mad.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-11-17 04:22:21 | Re: Attempt to consolidate reading of XLOG page |
| Previous Message | Steve Singer | 2019-11-17 00:53:27 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |