Re: error handling in RegisterBackgroundWorker - Mailing list pgsql-hackers

From Robert Haas
Subject Re: error handling in RegisterBackgroundWorker
Date
Msg-id CA+TgmoY13ti6s+MXK0ZosB3nKeYNjAsjnMv10mE7+eaELYivsw@mail.gmail.com
Whole thread Raw
In response to [HACKERS] error handling in RegisterBackgroundWorker  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: error handling in RegisterBackgroundWorker  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Wed, Mar 29, 2017 at 2:10 PM, Peter Eisentraut
<peter.eisentraut@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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Schedule and Release Management Team for PG10
Next
From: Stephen Frost
Date:
Subject: Re: [PATCH] Reduce src/test/recovery verbosity