pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16393: PANIC: cannot abort transaction, it was already committed
4+ messages / 4 participants
[nested] [flat]
* BUG #16393: PANIC: cannot abort transaction, it was already committed
@ 2020-04-27 09:19 PG Bug reporting form <noreply@postgresql.org>
2020-04-27 12:37 ` Re: BUG #16393: PANIC: cannot abort transaction, it was already committed Tom Lane <tgl@sss.pgh.pa.us>
2020-05-04 16:14 ` Re: BUG #16393: PANIC: cannot abort transaction, it was already committed Andres Freund <andres@anarazel.de>
0 siblings, 2 replies; 4+ messages in thread
From: PG Bug reporting form @ 2020-04-27 09:19 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: andreas.seltenreich@credativ.de
The following bug has been logged on the website:
Bug reference: 16393
Logged by: Andreas Seltenreich
Email address: andreas.seltenreich@credativ.de
PostgreSQL version: 11.5
Operating system: AIX
Description:
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
IIUC backporting was considered but deemed unreasonable here:
https://postgr.es/m/20190407203315.6v3iktksr5u3bksw@alap3.anarazel.de
Backtrace below.
regards,
Andreas
(dbx) where
abort()
pq_getmsgtext()
errposition()
IPRA.$AtCleanup_Memory()
StartTransaction()
DefineSavepoint()
IPRA.$exec_stmt_block()
pl_exec.IPRA.$exec_stmt_raise.exec_stmt()
pl_exec.IPRA.$exec_stmt_raise.IPRA.$exec_stmts()
IPRA.$exec_stmt_block()
plpgsql_exec_function()
plpgsql_call_handler()
ExecInterpExpr()
ExecEvalConstraintNotNull@AF173_67()
ExecInitProjectSet()
MultiExecProcNode()
IPRA.$InitPlan()
IPRA.$ExecBuildAggTransCall()
PortalRunFetch()
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
2020-04-27 09:19 BUG #16393: PANIC: cannot abort transaction, it was already committed PG Bug reporting form <noreply@postgresql.org>
@ 2020-04-27 12:37 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-05-05 20:44 ` Re: BUG #16393: PANIC: cannot abort transaction, it was already committed Andreas Seltenreich <andreas.seltenreich@credativ.de>
1 sibling, 1 reply; 4+ messages in thread
From: Tom Lane @ 2020-04-27 12:37 UTC (permalink / raw)
To: andreas.seltenreich@credativ.de; +Cc: pgsql-bugs@lists.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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
2020-04-27 09:19 BUG #16393: PANIC: cannot abort transaction, it was already committed PG Bug reporting form <noreply@postgresql.org>
2020-04-27 12:37 ` Re: BUG #16393: PANIC: cannot abort transaction, it was already committed Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-05-05 20:44 ` Andreas Seltenreich <andreas.seltenreich@credativ.de>
0 siblings, 0 replies; 4+ messages in thread
From: Andreas Seltenreich @ 2020-05-05 20:44 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; Andres Freund <andres@anarazel.de>; +Cc: pgsql-bugs@lists.postgresql.org
Tom Lane writes:
> 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?
I did inquire about getting my hands on the schema or a shell to a test
instance of the database for further analysis, but it's difficult as the
system is highly guarded by our customer. I'm afraid I won't be able to
contribute more info until then.
Andres Freund writes:
> On 2020-04-27 09:19:05 +0000, PG Bug reporting form wrote:
>> 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?
That was just my superficial impression after looking at recipe and
backtrace of #15727 (IIRC an error occures during error handling leading
to the same panic). I communicated to the customer that it's not clear
to me whether they are actually related but somehow I worded the bug
report with more prejudice than I intended, probably out of hope for a
quick backport fix. Your not seeing it squashed that though :-)
thanks,
Andreas
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #16393: PANIC: cannot abort transaction, it was already committed
2020-04-27 09:19 BUG #16393: PANIC: cannot abort transaction, it was already committed PG Bug reporting form <noreply@postgresql.org>
@ 2020-05-04 16:14 ` Andres Freund <andres@anarazel.de>
1 sibling, 0 replies; 4+ messages in thread
From: Andres Freund @ 2020-05-04 16:14 UTC (permalink / raw)
To: andreas.seltenreich@credativ.de; pgsql-bugs@lists.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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2020-05-05 20:44 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-04-27 09:19 BUG #16393: PANIC: cannot abort transaction, it was already committed PG Bug reporting form <noreply@postgresql.org>
2020-04-27 12:37 ` Re: BUG #16393: PANIC: cannot abort transaction, it was already committed Tom Lane <tgl@sss.pgh.pa.us>
2020-05-05 20:44 ` Re: BUG #16393: PANIC: cannot abort transaction, it was already committed Andreas Seltenreich <andreas.seltenreich@credativ.de>
2020-05-04 16:14 ` Andres Freund <andres@anarazel.de>
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