| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: error handling in RegisterBackgroundWorker |
| Date: | 2017-04-11 01:36:59 |
| Message-ID: | 3bb07215-05e8-7750-d87c-ce07c62ba5cc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/9/17 22:40, Noah Misch wrote:
> Agreed. There are times when starting up degraded beats failing to start,
> particularly when the failing component has complicated dependencies. In this
> case, as detailed upthread, this can only fail in response to basic
> misconfiguration. It's not the kind of thing that will spontaneously fail
> after a minor upgrade, for example.
If history had been different, we could have implemented, say,
autovacuum or walreceiver on the background worker framework. I think
unifying some of that might actually be a future project. Would it be
OK if these processes just logged a warning and didn't start if there
was a misconfiguration?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-11 01:41:27 | Re: Repetitive code in RI triggers |
| Previous Message | Michael Paquier | 2017-04-11 01:26:23 | Re: [PATCH v1] Add and report the new "in_hot_standby" GUC pseudo-variable. |