On Wed, Mar 29, 2017 at 2:10 PM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > How specifically would we do that? And what user would choose the > behavior "start this background worker but don't worry if it doesn't work"?
Well, if the background worker is auto-prewarm, you'd probably rather have the database start rather than get unhappy about auto-prewarm failing. If the background worker is your logical replication launcher it's a bit more serious, but if you have no subscriptions or they're not that critical, maybe you don't care. If the background worker is in charge of telling your failover solution that this node is up, then starting without it is entirely pointless. I would be inclined to leave this alone for now and revisit it for a future release. I don't feel confident that we really know what the right thing to do is here. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers