| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 03:50:21 |
| Message-ID: | 20190514035021.x5nsxbslr2pnuflo@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-05-14 04:09:16 | Re: VACUUM can finish an interrupted nbtree page split -- is that okay? |
| Previous Message | Michael Paquier | 2019-05-14 03:50:09 | Re: [HACKERS] Unlogged tables cleanup |