Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jW4RE-0002cN-1j for pgsql-bugs@arkaria.postgresql.org; Tue, 05 May 2020 20:45:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jW4RB-0006de-41 for pgsql-bugs@arkaria.postgresql.org; Tue, 05 May 2020 20:45:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jW4RA-0006dX-UJ for pgsql-bugs@lists.postgresql.org; Tue, 05 May 2020 20:45:08 +0000 Received: from mail.credativ.com ([2a02:158:380:2a0::5d5e:825a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jW4R7-000245-N3 for pgsql-bugs@lists.postgresql.org; Tue, 05 May 2020 20:45:07 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.credativ.com (Postfix) with ESMTP id 93502202A1; Tue, 5 May 2020 20:45:00 +0000 (UTC) X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc" Received: from mail.credativ.com ([127.0.0.1]) by localhost (mail.credativ.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eq_SJwnHgWBr; Tue, 5 May 2020 20:44:54 +0000 (UTC) Received: from snipe (unknown [IPv6:2003:5b:203b:200::10:12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: ase) by mail.credativ.com (Postfix) with ESMTPSA id 31713200B1; Tue, 5 May 2020 20:44:54 +0000 (UTC) From: Andreas Seltenreich To: Tom Lane , Andres Freund Cc: pgsql-bugs@lists.postgresql.org Cc: dubravko.fulir@gmail.com Subject: Re: BUG #16393: PANIC: cannot abort transaction, it was already committed References: <16393-0f4393a709445302@postgresql.org> <5057.1587991042@sss.pgh.pa.us> X-PGP-Key: 4096R/803D1FFF 2015-02-04 Key fingerprint = 4758 81DC 8539 494D 29B4 692D F587 0601 803D 1FFF Date: Tue, 05 May 2020 22:44:52 +0200 In-Reply-To: <5057.1587991042@sss.pgh.pa.us> (Tom Lane's message of "Mon, 27 Apr 2020 08:37:22 -0400") Message-ID: <87zham5cxn.fsf@credativ.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Tom Lane writes: > PG Bug reporting form 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