From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: r.zharkov@postgrespro.ru, Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
Date: Tue, 02 Apr 2019 13:30:56 -0400
Message-ID: <2120.1554226256@sss.pgh.pa.us> (raw)
In-Reply-To: <20190402171714.6mlldbvm32w727lk@alap3.anarazel.de>
References: <30650.1554219866@sss.pgh.pa.us>
<20190402155108.GA17787@alvherre.pgsql>
<20190402161320.o5wkbp7evuzqe4c2@alap3.anarazel.de>
<b5d89910ec01a657530d1a49ff0e05dc@postgrespro.ru>
<1492.1554225238@sss.pgh.pa.us>
<20190402171714.6mlldbvm32w727lk@alap3.anarazel.de>
Andres Freund <andres@anarazel.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
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, alvherre@2ndquadrant.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
In-Reply-To: <2120.1554226256@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