From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Thunder <thunder1(at)126(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PANIC :Call AbortTransaction when transaction id is no normal |
Date: | 2019-05-14 14:25:50 |
Message-ID: | 14904.1557843950@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Wong | 2019-05-14 14:31:40 | Re: Why is infinite_recurse test suddenly failing? |
Previous Message | Ashutosh Bapat | 2019-05-14 14:11:39 | Re: [HACKERS] advanced partition matching algorithm for partition-wise join |