From: Andres Freund <andres@anarazel.de>
To: andreas.seltenreich@credativ.de
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
Date: Mon, 4 May 2020 09:14:59 -0700
Message-ID: <20200504161459.xt46cdo2t3desphr@alap3.anarazel.de> (raw)
In-Reply-To: <16393-0f4393a709445302@postgresql.org>
References: <16393-0f4393a709445302@postgresql.org>
Hi,
On 2020-04-27 09:19:05 +0000, PG Bug reporting form wrote:
> One of our customers recently experienced the following PANIC with
> PostgreSQL 11.5 on AIX:
>
> PANIC: cannot abort transaction 1234567890, it was already committed
> CONTEXT: PL/pgSQL function foo.bar(varchar[],…,timestamptz[]) line 5 during
> exception cleanup
> STATEMENT: PREPARE q1 (varchar,[...],timestamptz) AS select
> foo.bar(ARRAY[$1, …], …, $101], ARRAY[$102, $103])
>
> There is a striking similarity to BUG #15727 from 2019 where this
> PANIC also occured during error handling. Archive link to the old
> bug: https://postgr.es/m/15727-0be246e7d852d229@postgresql.org
It doesn't immediately see that similar to me. What makes you think it
is?
Greetings,
Andres Freund
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, andreas.seltenreich@credativ.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
In-Reply-To: <20200504161459.xt46cdo2t3desphr@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