From: Tom Lane <tgl@sss.pgh.pa.us>
To: andreas.seltenreich@credativ.de
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
Date: Mon, 27 Apr 2020 08:37:22 -0400
Message-ID: <5057.1587991042@sss.pgh.pa.us> (raw)
In-Reply-To: <16393-0f4393a709445302@postgresql.org>
References: <16393-0f4393a709445302@postgresql.org>
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
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, andreas.seltenreich@credativ.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
In-Reply-To: <5057.1587991042@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