Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WAMea-0008Hl-Uf for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Feb 2014 16:45:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WAMea-0003tH-EA for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Feb 2014 16:45:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WAMeZ-0003t9-KN for pgsql-hackers@postgresql.org; Mon, 03 Feb 2014 16:45:47 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WAMeX-0002GO-Fn for pgsql-hackers@postgresql.org; Mon, 03 Feb 2014 16:45:47 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s13Gjhpe032579; Mon, 3 Feb 2014 11:45:43 -0500 From: Tom Lane To: Robert Haas cc: Antonin Houska , "pgsql-hackers@postgresql.org" Subject: Re: bgworker crashed or not? In-reply-to: References: <52EBE0E0.8040303@gmail.com> <30853.1391440857@sss.pgh.pa.us> <32224.1391444962@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Mon, 03 Feb 2014 11:34:14 -0500" Date: Mon, 03 Feb 2014 11:45:43 -0500 Message-ID: <32578.1391445943@sss.pgh.pa.us> X-Pg-Spam-Score: -2.4 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Robert Haas writes: > On Mon, Feb 3, 2014 at 11:29 AM, Tom Lane wrote: >> Agreed, but after further reflection it seems like if you've declared >> a restart interval, then "done until restart interval" is probably the >> common case. So how about ... > I think what I proposed is better for two reasons: > 1. It doesn't change the meaning of exit(1) vs. 9.3. All background > worker code I've seen or heard about (which is admittedly not all > there is) does exit(1) because the current exit(0) behavior doesn't > seem to be what anyone wants. Hm. If that's actually the case, then I agree that preserving the current behavior of exit(1) is useful. I'd been assuming we were breaking things anyway. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers