Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQYNh-0003cN-C5 for pgsql-hackers@arkaria.postgresql.org; Tue, 14 May 2019 14:26:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hQYNg-0001uy-1U for pgsql-hackers@arkaria.postgresql.org; Tue, 14 May 2019 14:26:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQYNf-0001uq-Lj for pgsql-hackers@lists.postgresql.org; Tue, 14 May 2019 14:26:11 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQYNa-0006t2-0C for pgsql-hackers@lists.postgresql.org; Tue, 14 May 2019 14:26:10 +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 x4EEPojL014905; Tue, 14 May 2019 10:25:50 -0400 From: Tom Lane To: Andres Freund cc: Michael Paquier , Thunder , Kuntal Ghosh , PostgreSQL Hackers Subject: Re: PANIC :Call AbortTransaction when transaction id is no normal In-reply-to: <20190514035021.x5nsxbslr2pnuflo@alap3.anarazel.de> References: <3850b11a.5121.16aaf827e4a.Coremail.thunder1@126.com> <20190513081018.GC2273@paquier.xyz> <15939.1557754652@sss.pgh.pa.us> <20190513235336.GE2273@paquier.xyz> <4d8688e8.2ed3.16ab444bc37.Coremail.thunder1@126.com> <13093.1557804531@sss.pgh.pa.us> <20190514033739.GH1418@paquier.xyz> <20190514035021.x5nsxbslr2pnuflo@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Mon, 13 May 2019 20:50:21 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14903.1557843950.1@sss.pgh.pa.us> Date: Tue, 14 May 2019 10:25:50 -0400 Message-ID: <14904.1557843950@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2019-05-14 12:37:39 +0900, Michael Paquier wrote: >> Still, I would like to understand why the bootstrap process has been >> signaled to begin with, particularly for an initdb, which is not >> really something that should happen on a server where an instance >> runs. If you have a too aggressive monitoring job, you may want to >> revisit that as well, because it is able to complain just with an >> initdb. > Shutdown, timeout, resource exhaustion all seem like possible > causes. Don't think any of them warrant a core file - as the OP > explains, that'll often trigger pages etc. Yeah. The case I was thinking about was mostly "start initdb, decide I didn't want to do that, hit control-C". That cleans up without much fuss *except* if you manage to hit the window where it's running bootstrap, and then it spews this scary-looking error. It's less scary-looking with the SIG_DFL patch, which I've now pushed. regards, tom lane