Re: BUG #16393: PANIC: cannot abort transaction, it was already committed - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
Date
Msg-id 5057.1587991042@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16393: PANIC: cannot abort transaction, it was already committed  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.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



pgsql-bugs by date:

Previous
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: [BUG] non archived WAL removed during production crash recovery
Next
From: PG Bug reporting form
Date:
Subject: BUG #16395: error when selecting generated column in a foreign table