Re: PANIC :Call AbortTransaction when transaction id is no normal - Mailing list pgsql-hackers

From Andres Freund
Subject Re: PANIC :Call AbortTransaction when transaction id is no normal
Date
Msg-id 20190514035021.x5nsxbslr2pnuflo@alap3.anarazel.de
Whole thread Raw
In response to Re: PANIC :Call AbortTransaction when transaction id is no normal  (Michael Paquier <michael@paquier.xyz>)
Responses Re: PANIC :Call AbortTransaction when transaction id is no normal  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

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.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Unlogged tables cleanup
Next
From: Peter Geoghegan
Date:
Subject: Re: VACUUM can finish an interrupted nbtree page split -- is that okay?