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 1nd3Ha-0006FT-Aa for pgsql-hackers@arkaria.postgresql.org; Sat, 09 Apr 2022 05:05:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nd3HZ-0004hw-6S for pgsql-hackers@arkaria.postgresql.org; Sat, 09 Apr 2022 05:05:09 +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 1nd3HY-0004hm-Tm for pgsql-hackers@lists.postgresql.org; Sat, 09 Apr 2022 05:05:08 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nd3HW-00006j-QM for pgsql-hackers@postgresql.org; Sat, 09 Apr 2022 05:05:08 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id E84683201F01; Sat, 9 Apr 2022 01:05:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 09 Apr 2022 01:05:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= 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=fm1; bh=Y1D8jqBMiO2b0CcqXzxM8c7ofU7QUDUAbL0HZ4 WV3cg=; b=4luBLSeGhlQwHazbDj7Qc40NM8KlEewq8SMoPpJEiPC34Jz7CNxn8Y WbP3yAc7pfc0AGlcy0Igtw/jP9zBYhPJLi1b84lLU1JLOcwnhhrq2Z6Pig78hkDW 4AbvajKW8mPh3XuE8iwBx9sDTSlBlN5PuGmTk8g9M7FrQQGG29kOOOR4BYw0/Vk3 l0/gbGatoutwe53m2PqcxP/t9JLQw6xz9u41lWvC3JnTMGXxGA1DdMPcIbFlisUP vdmopEfPtNWb30q0WKK4+fEcoHy4uton+SScVOvzAjgLJ551aAypAf2BMuHT4jTr rXwdXt9eVrhfgEut6N2fTVtznJSbDcpQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Y1D8jqBMiO2b0CcqX zxM8c7ofU7QUDUAbL0HZ4WV3cg=; b=oZSfsvyUfliB1HOkfk88jyE/OaLGuwpsB oCseV1wgPb2zlGxRX/ZHeGWfRvHU2Ea3/+amQz+UB0vH9FFY0cmxt1TrZRWOiJDO UHSpZzLkW0fF41/DK6Vforbm2SQ2ezz7inJF9/JzY/toK3ZSbXYOLpHgQ0cXORqS YVEDTX6y3ixVoW64ovBjx/wDFHV2y4liDu3GmVX3ipia7oZChQrJRonOZFtdh2ej 4/Cjh9pzbuo8O9J9qOhgNCg7G4isRbMbtPWZyTRWhEUKokcOoYvohNNuTdbbawqU I3WoIgkaabo5ZiU8ISpls/qs+OXyWYcdZ+ISYoMKhCfo7aFweBijQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudekuddgkeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgurhgv shcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucggtffrrg htthgvrhhnpedukefhkeelueegveetheelffffjeegleeuudelfeefuedtleffueejfffh ueffudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe grnhgurhgvshesrghnrghrrgiivghlrdguvg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 9 Apr 2022 01:05:02 -0400 (EDT) Date: Fri, 8 Apr 2022 22:05:01 -0700 From: Andres Freund To: pgsql-hackers@postgresql.org, Thomas Munro Subject: Re: failures in t/031_recovery_conflict.pl on CI Message-ID: <20220409050501.frejv2i46m54keem@alap3.anarazel.de> References: <20220409045515.35ypjzddp25v72ou@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220409045515.35ypjzddp25v72ou@alap3.anarazel.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2022-04-08 21:55:15 -0700, Andres Freund wrote: > on CI [1] the new t/031_recovery_conflict.pl is failing occasionally. Which is > interesting, because I ran it there dozens if not hundreds of times before > commit, with - I think - only cosmetic changes. Scratch that part - I found an instance of the freebsd failure earlier, just didn't notice because that run failed for other reasons as well. So this might just have uncovered an older bug around recovery conflict handling, potentially platform dependent. I guess I'll try to reproduce it on freebsd... Greetings, Andres Freund