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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
