Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBN2J-0006KK-RS for pgsql-bugs@arkaria.postgresql.org; Tue, 02 Apr 2019 17:17:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hBN2I-0003YR-AX for pgsql-bugs@arkaria.postgresql.org; Tue, 02 Apr 2019 17:17:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBN2I-0003YK-38 for pgsql-bugs@lists.postgresql.org; Tue, 02 Apr 2019 17:17:22 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hBN2F-00038V-Ch for pgsql-bugs@lists.postgresql.org; Tue, 02 Apr 2019 17:17:21 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id DE11F3275; Tue, 2 Apr 2019 13:17:16 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 02 Apr 2019 13:17:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=aOVlwKzZLrmy7w08YO+OkpgXnQN n8Nqh6I2tIUp00GQ=; b=kiObb39glq/PQRherX9S8rVkyLEKdzcTYemFHc6yVEB I9ZS/u1kEk4ZpZoK5b2MV0CgaMwBjMasJErCR+/rZySmSHRmoAxg3JKPrs7/tLdh pdS49z5dIt7GFbshnka+2DtSb6corRjSKNBEfsHVoAA3NmYfK2MP2KMcqcx/hpcM mAe31sz00KiEsTdZDgjAlateQ/uu4RkLsbyVj0Byqs9CHOzoP0o5dP6dxfyuEN/q jhx4gG/q1Iy7g9J6w6Ol5MgaUW153ERQOjzgOqGbGgoO0/Uzd8Wf7sNke2YNf9lW SCDuoqxjaA5igpSg4/2aXLrOfPHR7tOgfvOXdQHDxzQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=aOVlwK zZLrmy7w08YO+OkpgXnQNn8Nqh6I2tIUp00GQ=; b=ft8fL7/Zm7/ShKpbL+BCQD /axFTNZCbjMFNr80mTbZArVqEMMQqOUWpUjMN0mOvtM9e8ztbcZAHvZRiPgKjlao vRVKRjtH5iJhipcHD1uylllzUZB6f0kTkcoOUFvu6IqJlRe2k/VMlPAB4xzMJPlY /S2MNpcff32SMfLboUnYYMpME1Hm181PvZr19j11ZQcUMB75Po8DCI4rk9vGlFjT y7BMWIXCCV4rQcQBnSVMu+jHtwugjVzV5hzsC02zXEePkiGYOsXPk+lhkMC1YYKt 8CvBgwQUQ0gN5MPOgNFJ+6K0I9hhMAo74TCtUIi4VMsZnDHpfr7aN3a0Og3tSsrg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrtddtgdeludculddtuddrgedutddrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfhggtggujgesthdtredttddtvden ucfhrhhomheptehnughrvghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivg hlrdguvgeqnecukfhppeelkedrvddutddrudegtddrudejudenucfrrghrrghmpehmrghi lhhfrhhomheprghnughrvghssegrnhgrrhgriigvlhdruggvnecuvehluhhsthgvrhfuih iivgeptd X-ME-Proxy: Received: from intern.anarazel.de (c-98-210-140-171.hsd1.ca.comcast.net [98.210.140.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 508E410392; Tue, 2 Apr 2019 13:17:15 -0400 (EDT) Date: Tue, 2 Apr 2019 10:17:14 -0700 From: Andres Freund To: Tom Lane Cc: r.zharkov@postgrespro.ru, Alvaro Herrera , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed Message-ID: <20190402171714.6mlldbvm32w727lk@alap3.anarazel.de> References: <30650.1554219866@sss.pgh.pa.us> <20190402155108.GA17787@alvherre.pgsql> <20190402161320.o5wkbp7evuzqe4c2@alap3.anarazel.de> <1492.1554225238@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1492.1554225238@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, On 2019-04-02 13:13:58 -0400, Tom Lane wrote: > FWIW, I see six potential candidates, not two: > > pgsql/src/backend/commands/trigger.c: 3380: elog(ERROR, "unexpected table_lock_tuple status: %u", test); > pgsql/src/backend/executor/nodeLockRows.c: 232: elog(ERROR, "unexpected table_lock_tuple status: %u", > pgsql/src/backend/executor/execReplication.c: 211: elog(ERROR, "unexpected table_lock_tuple status: %u", res); > pgsql/src/backend/executor/execReplication.c: 375: elog(ERROR, "unexpected table_lock_tuple status: %u", res); These have an explicit case / separate error for TM_Invisible (= 1 - which is the status we're seeing according to the error message) though. So afaict they can't be relevant here. Greetings, Andres Freund