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 1oGQmr-000410-PX for pgsql-hackers@arkaria.postgresql.org; Tue, 26 Jul 2022 20:04:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oGQmq-0004em-6c for pgsql-hackers@arkaria.postgresql.org; Tue, 26 Jul 2022 20:04:12 +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 1oGQmo-0004ec-FC for pgsql-hackers@lists.postgresql.org; Tue, 26 Jul 2022 20:04:11 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oGQme-000216-NY for pgsql-hackers@lists.postgresql.org; Tue, 26 Jul 2022 20:04:08 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 87E6D5C00DA; Tue, 26 Jul 2022 16:03:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Tue, 26 Jul 2022 16:03:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1658865837; x=1658952237; bh=hHxTqy9mb/ pVCF7++d3eS+om9Quujd7cI60YjzLl2sE=; b=bQauCG4cGlR+UI9DoEzpo9y8dV g688MJim5h6KeqsbT/OhBNEY8DKFKXjl+JM4/9SnK6RDxlJiwFqeayp1a0nNNPZk ZWly808NBEqnyjrnvDNoC1XmC8oB5G4O9LKC+z+m61frKTM8FCk9+cagZoFE4FMd PdgO/bwoCu2zKeSDdIl8hoWid6YTi0IzvU0yLN/gqT7kfGehhEaSPYE0MlZlT6E5 hleIy2lzQF+dh9eNnYocTgaQ4evnjdXyjg2xadG0tq6aDyMbC85uXHN3NHaCPYRp 7VAuTWjldiv/BvP1Okw3UbTNZD9hwx9QbDLP99aC+UC1VwvdaBVkxrTqPzaA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1658865837; x=1658952237; bh=hHxTqy9mb/pVCF7++d3eS+om9Quu jd7cI60YjzLl2sE=; b=euiqZLd/avpoif3XKMbanS0rz3/Z6PfPNv5e52bztR1e xL45SnA/Xz4zLV1IUQ1nCUBT8yY6pCrGYtyaewvJJKa1Hgdk362gOWkthJeV6oUB HwnpyblyQABTTbkbxbIduuGekIvcdVbzXeSVQdQBeeHQzJb5BJyE5T5YDW7Sfrp3 vzTe9jTUttIKUXhCbeaGU5vROU3Jj/KeAw7mGTfNKQRNmMXeEDbX8r/HstKESGko uU2RGjOxVhqj4mACjYFqd9PdG+qwOETyp2+Xpv4evjzSDNNAbRYauACruJFoE7PM SsVNo47AB0v9gZ5/Es8A2OOpO4kWwceC6i5fTCr4sQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvddutddgudegiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgu rhgvshcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucggtf frrghtthgvrhhnpedvffefvefhteevffegieetfefhtddvffejvefhueetgeeludehteev udeitedtudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpegrnhgurhgvshesrghnrghrrgiivghlrdguvg X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 26 Jul 2022 16:03:56 -0400 (EDT) Date: Tue, 26 Jul 2022 13:03:54 -0700 From: Andres Freund To: Tom Lane Cc: Thomas Munro , Melanie Plageman , pgsql-hackers@lists.postgresql.org Subject: Re: Unstable tests for recovery conflict handling Message-ID: <20220726200354.hunrcu6zfjakxfnk@alap3.anarazel.de> References: <394950.1651077914@sss.pgh.pa.us> <447238.1651082925@sss.pgh.pa.us> <2454340.1658858273@sss.pgh.pa.us> <20220726181611.4xw3blxigqzsz4d4@alap3.anarazel.de> <2468550.1658860230@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2468550.1658860230@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2022-07-26 14:30:30 -0400, Tom Lane wrote: > Andres Freund writes: > > On 2022-07-26 13:57:53 -0400, Tom Lane wrote: > >> So this is not a case of RecoveryConflictInterrupt doing the wrong thing: > >> the startup process hasn't detected the buffer conflict in the first > >> place. > > > I wonder if this, at least partially, could be be due to the elog thing > > I was complaining about nearby. I.e. we decide to FATAL as part of a > > recovery conflict interrupt, and then during that ERROR out as part of > > another recovery conflict interrupt (because nothing holds interrupts as > > part of FATAL). > > There are all sorts of things one could imagine going wrong in the > backend receiving the recovery conflict interrupt, but AFAICS in these > failures, the startup process hasn't sent a recovery conflict interrupt. > It certainly hasn't logged anything suggesting it noticed a conflict. I don't think we reliably emit a log message before the recovery conflict is resolved. I've wondered a couple times now about making tap test timeouts somehow trigger a core dump of all processes. Certainly would make it easier to debug some of these kinds of issues. Greetings, Andres Freund