Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: r(dot)zharkov(at)postgrespro(dot)ru, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
Date: 2019-04-02 17:30:56
Message-ID: 2120.1554226256@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2019-04-02 13:13:58 -0400, Tom Lane wrote:
>> FWIW, I see six potential candidates, not two:

> These have an explicit case / separate error for TM_Invisible (= 1 -
> which is the status we're seeing according to the error message)
> though. So afaict they can't be relevant here.

Oh, right, so it has to be from one of the calls in nodeModifyTable.c.
But it's hardly plausible that that runs post-commit. So now I'm
thinking that what we really need to know is why a TM_Invisible
result was returned. That's going to be a bit harder ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Жарков Роман 2019-04-02 17:35:47 Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
Previous Message Alvaro Herrera 2019-04-02 17:17:21 Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed