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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: andreas(dot)seltenreich(at)credativ(dot)de
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
Date: 2020-04-27 12:37:22
Message-ID: 5057.1587991042@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> One of our customers recently experienced the following PANIC with
> PostgreSQL 11.5 on AIX:
> PANIC: cannot abort transaction 1234567890, it was already committed

That's probably just a side-effect of some other problem. There's
no strong reason to think that it's the same thing as #15727.
Can you provide a reproducer by any chance?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-04-27 14:24:02 BUG #16395: error when selecting generated column in a foreign table
Previous Message Jehan-Guillaume de Rorthais 2020-04-27 10:42:47 Re: [BUG] non archived WAL removed during production crash recovery