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

From Andres Freund
Subject Re: BUG #16393: PANIC: cannot abort transaction, it was alreadycommitted
Date
Msg-id 20200504161459.xt46cdo2t3desphr@alap3.anarazel.de
Whole thread Raw
In response to BUG #16393: PANIC: cannot abort transaction, it was already committed  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: VS: BUG #16404: PostgreSQL 12.2: Database restore does not accept the EEST time zone.
Next
From: PG Bug reporting form
Date:
Subject: BUG #16416: unable to start the server with pg_CTL