Re: [HACKERS] error handling in RegisterBackgroundWorker - Mailing list pgsql-hackers

From Noah Misch
Subject Re: [HACKERS] error handling in RegisterBackgroundWorker
Date
Msg-id 20170412021302.GA2890773@tornado.leadboat.com
Whole thread Raw
In response to Re: [HACKERS] error handling in RegisterBackgroundWorker  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] error handling in RegisterBackgroundWorker  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Tue, Apr 11, 2017 at 11:33:34AM -0400, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> > I think there is no clear agreement here, and no historically consistent
> > behavior.  I'm prepared to let it go and cross it off the list of open
> > items.  I believe we should keep thinking about it, but it's not
> > something that has to hold up beta.
> 
> Agreed, this doesn't seem like a must-fix-for-beta consideration.

Definitely not a beta blocker, agreed.  Would it be okay to release v10 final
with the logical replication launcher soft-failing this way?



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] Remove pg_stat_progress_vacuum from Table 28.2
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] Partitioned tables and relfilenode