From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Thunder <thunder1@126.com>
Cc: Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: PANIC :Call AbortTransaction when transaction id is no normal
Date: Tue, 14 May 2019 10:25:50 -0400
Message-ID: <14904.1557843950@sss.pgh.pa.us> (raw)
In-Reply-To: <20190514035021.x5nsxbslr2pnuflo@alap3.anarazel.de>
References: <3850b11a.5121.16aaf827e4a.Coremail.thunder1@126.com>
<CAGz5QCJKDptF4R0xHzM9YLxbLwZHA9enW9zjOi+vF93HVycVgw@mail.gmail.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>
Andres Freund <andres@anarazel.de> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, michael@paquier.xyz, thunder1@126.com, kuntalghosh.2007@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: PANIC :Call AbortTransaction when transaction id is no normal
In-Reply-To: <14904.1557843950@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox