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 1jVdkY-000691-Lw for pgsql-bugs@arkaria.postgresql.org; Mon, 04 May 2020 16:15:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jVdkX-0000tm-HJ for pgsql-bugs@arkaria.postgresql.org; Mon, 04 May 2020 16:15:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jVdkV-0000tf-MK for pgsql-bugs@lists.postgresql.org; Mon, 04 May 2020 16:15:21 +0000 Received: from [66.111.4.27] (helo=out3-smtp.messagingengine.com) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jVdkR-0001Qq-82 for pgsql-bugs@lists.postgresql.org; Mon, 04 May 2020 16:15:19 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 5C35A5C0032; Mon, 4 May 2020 12:15:03 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 04 May 2020 12:15:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:subject:message-id:references:mime-version :content-type:content-transfer-encoding:in-reply-to; s=fm1; bh=R 41eUlpa1wI5cIDqy7+SEQM7gK3xuJuAy0KFqT80aL8=; b=LxhUetgKLwfEPawGT q/TNvm8+kDZmMlY1QBdGc4DTG4ZXo0UsUqYJeZR0AiZfUExexcg5v55mnqWXvZQa doG1c2V+FGokWlhe3w2eKtTtgSrMY0o4XHBrADAVuO3rIIKjI5oLEU7hzeM1DUja 0n4RPjk//g9awUDxcH0M/PaHaP+qe2kPUuRnCWFhDTEqnbl0aSqbN8j21olTrwOp q4oi/0gFt95NlQq1j6Cl2L0OEtJPSchcfrYYXid9x9Tnds2JXNwPAMlyMta94nVm oKJCUVA1XJnaj4+FnohezI+UnpXCk6W5LmOq6NyturgZTlqVmyigJXt7F9XcH5YQ Aiv7A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=R41eUlpa1wI5cIDqy7+SEQM7gK3xuJuAy0KFqT80a L8=; b=iMbLEjqw+wiGtp1gQS5vyJ7WTwpBed0FlNQFYWmaUHP6u4DoLukVaFP0p 6dgj6o08mirAGmaYTpAYLnOgGLgVAyZRvUQmtug/+f5xX+LoXke+vw+UcPHW0oe2 bcTrGaN6SJxmLKAK11gzjKh1IIwgJ+2kDfyE4n/6OIl+vpoVi36a307Bn/3Mpw0M +rbJgXtWTmdyOXWbv6O5vHWa54r5YllXXOGtS10hqioxJW06LQqclQNzC4/rUSKl rl3r1w1stydyDN/l2yFacwpl4pbI3WwJ3GxUYV8dlpcfVHYARMKXr0Umli1CYv5H Y7AWHh/md2J3Nhpkk9tr1sUn9mL/A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrjeeggdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtugfgjgesthekre dttddtjeenucfhrhhomheptehnughrvghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghn rghrrgiivghlrdguvgeqnecuggftrfgrthhtvghrnhepvefhiefgffduuedvheegjeekvd ejueeggfefheeifedulefffedvjeegjefhveevnecuffhomhgrihhnpehpohhsthhgrhdr vghsnecukfhppeeijedrudeitddrvddujedrvdehtdenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrnhgurhgvshesrghnrghrrgiivghlrdgu vg X-ME-Proxy: Received: from intern.anarazel.de (c-67-160-217-250.hsd1.ca.comcast.net [67.160.217.250]) by mail.messagingengine.com (Postfix) with ESMTPA id 23F273065FFD; Mon, 4 May 2020 12:15:01 -0400 (EDT) Date: Mon, 4 May 2020 09:14:59 -0700 From: Andres Freund To: andreas.seltenreich@credativ.de, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16393: PANIC: cannot abort transaction, it was already committed Message-ID: <20200504161459.xt46cdo2t3desphr@alap3.anarazel.de> References: <16393-0f4393a709445302@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16393-0f4393a709445302@postgresql.org> X-Host-Lookup-Failed: Reverse DNS lookup failed for 66.111.4.27 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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