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 1mVvn8-0006HJ-UZ for pgsql-committers@arkaria.postgresql.org; Thu, 30 Sep 2021 13:08:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mVvn7-00035S-S2 for pgsql-committers@arkaria.postgresql.org; Thu, 30 Sep 2021 13:08:01 +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 1mVvn7-00034U-1E for pgsql-committers@lists.postgresql.org; Thu, 30 Sep 2021 13:08:01 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mVvn4-000539-Dd for pgsql-committers@lists.postgresql.org; Thu, 30 Sep 2021 13:08:00 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 19F093201AED; Thu, 30 Sep 2021 09:07:56 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 30 Sep 2021 09:07:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=6j2XcBiB+9+qK8szSctYVotMzB6NYZ3Gz8xF7YE4+7M=; b=pNYA3ESa HK9w+3N0iS8FnmF6lD+h4of24tWHhhDZc9esPLitp8WUSG/7bAYaGRYcIfSRFOnk vzbP1plE2E5guO0iciOzQ663tGZMlsyV+n5h77X3YsLlS0xXfk0s5SCIPkp0ReyW lYaY54ho7m3S4kWaBZJ6IHdFjnkkbmrGcVto4eW6AZAR3aFkdO5BbcxYW37amtAQ Ej3mIiAPOTF5YXPmUwaaIge/mCYSt8eMpb+dRKbvjF9TtgL9DvK8mjbxU52RCagu fqiPcaWDuzFLnjxMAccU6zWWc08FXFaU7W3t+ZpTOQBItWjswO/kXPecRSNXsiA2 9kPp3YVql+S7Cw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudekgedgheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpeelfeekhffgleetieegjeekvdejvdelhfeuheefvdejheeu teevteejkeeufffgheenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgpdgvnh htvghrphhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 30 Sep 2021 09:07:55 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 0EA442A06AB; Thu, 30 Sep 2021 10:07:51 -0300 (-03) Date: Thu, 30 Sep 2021 10:07:51 -0300 From: Alvaro Herrera To: Michael Paquier Cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Fix WAL replay in presence of an incomplete record Message-ID: <202109301307.gq4txat6pb4p@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Sep-30, Michael Paquier wrote: > Hi Alvaro, > > On Wed, Sep 29, 2021 at 02:40:29PM +0000, Alvaro Herrera wrote: > > Fix WAL replay in presence of an incomplete record > > [...] > > src/test/recovery/t/026_overwrite_contrecord.pl | 207 ++++++++++++++++++++++++ > > src/test/recovery/t/idiosyncratic_copy | 20 +++ > > The builfarm is saying that this test fails on Windows: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=jacana&dt=2021-09-29%2020%3A00%3A01 > Sep 29 17:27:23 t/026_overwrite_contrecord..........FAILED--Further testing stopped: command "pg_basebackup -D... > [...] > pg_basebackup: error: connection to server at "127.0.0.1", port 55644 failed: FATAL: no pg_hba.conf entry for replication connection from host "127.0.0.1", user "pgrunner", no encryption Thanks. We had already discussed this in the other thread and I opted to call ->set_replication_conf instead: https://www.postgresql.org/message-id/202109292127.7q66qhxhde67%40alvherre.pgsql According to Andres, there's still going to be a failure for other reasons, but let's see what happens. -- Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/ really, I see PHP as like a strange amalgamation of C, Perl, Shell inflex: you know that "amalgam" means "mixture with mercury", more or less, right? i.e., "deadly poison"