pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
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, 2 Apr 2019 10:17:14 -0700
Message-ID: <20190402171714.6mlldbvm32w727lk@alap3.anarazel.de> (raw)
In-Reply-To: <1492.1554225238@sss.pgh.pa.us>
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>

Hi,

On 2019-04-02 13:13:58 -0400, Tom Lane wrote:
> FWIW, I see six potential candidates, not two:
> 
> pgsql/src/backend/commands/trigger.c: 3380: 				elog(ERROR, "unexpected table_lock_tuple status: %u", test);
> pgsql/src/backend/executor/nodeLockRows.c: 232: 				elog(ERROR, "unexpected table_lock_tuple status: %u",
> pgsql/src/backend/executor/execReplication.c: 211: 				elog(ERROR, "unexpected table_lock_tuple status: %u", res);
> pgsql/src/backend/executor/execReplication.c: 375: 				elog(ERROR, "unexpected table_lock_tuple status: %u", res);

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.

Greetings,

Andres Freund





view thread (46+ messages)  latest in thread

Message-ID: <20190402171714.6mlldbvm32w727lk@alap3.anarazel.de>
Permalink:  ../20190402171714.6mlldbvm32w727lk@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20190402171714.6mlldbvm32w727lk@alap3.anarazel.de

 · 

reply

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: andres@anarazel.de, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
  In-Reply-To: <20190402171714.6mlldbvm32w727lk@alap3.anarazel.de>

* 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