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

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