Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sRK0u-00ETil-Ll for pgsql-bugs@arkaria.postgresql.org; Tue, 09 Jul 2024 23:12:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sRK0s-000huC-VO for pgsql-bugs@arkaria.postgresql.org; Tue, 09 Jul 2024 23:12:46 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sRK0s-000hu3-6U for pgsql-bugs@lists.postgresql.org; Tue, 09 Jul 2024 23:12:46 +0000 Received: from fhigh3-smtp.messagingengine.com ([103.168.172.154]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sRK0p-001IO3-HS for pgsql-bugs@lists.postgresql.org; Tue, 09 Jul 2024 23:12:45 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.nyi.internal (Postfix) with ESMTP id B7FE71140493; Tue, 9 Jul 2024 19:12:41 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 09 Jul 2024 19:12:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1720566761; x=1720653161; bh=tKaXsBPS8h S3UqRleXIRlk+G8SQb/lIoeCu4dhM6t0c=; b=1k6aEin4H0JC428xVZ+Ig1UmGx 6xhrrp+p4vAW6EXk/O/jjA55hWzB19tLK4YKcsi0U5M1dXQYYGwa196DQzdFdHBt 5wXWLhJ3PtCZbvIFCWJUr3VlzGzfQNzP84rECE3K4Jd/i6YCnYkRW0srH0XvGTGz /s2Mc33n0KHJGO8kNVURRINR8KbzRvETQHivsDNZLcmlCt+9xUZkOoyGnkJ+4mpn OGNiRB4JZMSK6eOsi+DKLfODOcgjnUkdQH/mbc3pq/kAQjdsIHgErjOTHHW6f0oJ e8PW1v8LaYY7yvgiMISef6bHSd+DPnQPEiI0YR2j4Pma4Lwze64PCzYIw/mQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1720566761; x=1720653161; bh=tKaXsBPS8hS3UqRleXIRlk+G8SQb /lIoeCu4dhM6t0c=; b=MCeHUBz5r5F1ASDnOjNFcJog57aJIlpHTEVKB8fVeE+/ mVbT51Fz0gBTBEz2TE3C6C/6PMkT2Tz/y9DVigjdp7JrrFF8L+JEXZi0gbPh5n4v IoVM4XVoZJGjcr+oD2ATb/XbXC57F2JtXC3ZANkaW6YuQcPeT841CGs4Tpjm5pJ5 CwGmkNqgeOqK6Y7axFI0K0Xh1d6QoPk+nu50NBcrIWP82v21xoL73JkwntaEwqcE g1cU3Jl2mIqMBFzIw5At4uVO29SK13PvN2XSGxXawnGyvIrineXR8cdC5UJ14K0i f49Z/vAgrRFUNnSZQjP4KX9yhPn2d/hpSpccBRBvgQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrfedtgddulecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdejtddmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeetleeifedufffhhfdtteelgeeg geffhfekueevteeigfduudevudetgfegiedvjeenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 9 Jul 2024 19:12:38 -0400 (EDT) Date: Wed, 10 Jul 2024 08:12:29 +0900 From: Michael Paquier To: Andrew Dunstan Cc: Chris Travers , Farooq Rashed , pgsql-bugs@lists.postgresql.org Subject: Re: pg_rewind fails on Windows where tablespaces are used Message-ID: References: <5169f6d5-240e-49ec-9265-ddafa6e863bd@dunslane.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MIIlTDOwAbcOUihE" Content-Disposition: inline In-Reply-To: <5169f6d5-240e-49ec-9265-ddafa6e863bd@dunslane.net> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --MIIlTDOwAbcOUihE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 09, 2024 at 12:01:17PM -0400, Andrew Dunstan wrote: > The solution I came up with was to backpatch commits c5cb8f3b, 387803d8 and > 5fc88c5d53. The lstat() wrapper for Windows, noted. > I don't think we need to do anything relating to in-place tablespaces. These > are documented as a developer only option and not for production. Okay, cool. > The only question in my mind is whether those patches should be > backpatched. > > It's a couple of hundred lines, and I think it's safe, but I'd welcome other > opinions. If we are going to backpatch them we should also look at adding to > adding tests for use of tablespaces with pg_rewind on the back branches. > Ideally we'd get this done in time for the next maintenance release. Seeing that the commits all go down to v16, meaning that these have brewed across 3 minor releases already, I'd like to assume that we would have already heard about problems related to them. So that seems like a rather safe thing to do at this stage. -- Michael --MIIlTDOwAbcOUihE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmaNw90ACgkQnvQgOdby QH1XpA/9G6WKiY5lyRG4EInU+Sh8KAxeafrXimrGwo0yfMaW1K05O8MPCJYNjs66 5Q7uljohvuYHnZssNlBdxQCpbr6TqtFKNisgsxutNZWOHwrtOLOsr9Mz585ayVVb 2qyQFdj2uNaBipor+Y8t1YqYwbEBGXzTcLds0PMBPvB8ZS0yuZleyZKn2EcRvo1h VTxwqqUt1fjB9h8JqNk5Xk4sC81eKnRXIL6oV3Ts1fyQRI60rnRJewjydfsYaVyR KoGP8OAnAy/u278G5ONwEY+ST7hxTCshU375wh8XL58CGN4zA8RQX6UCx+N16cHj IlK8CpRFFIAodCho81hSK6FOrgalrfdwtTKSzSsawDkupAmmfvNEWocg1n1RzK6m 13PfsFO96N4B+Zm/t7JyzPGn4ZID/RJhRRXMSqNHV9ZdjdnKkXgL17AaVIhtqsuQ eFOiXRFaOHzSlBDM5td+UVGte1VUIk8PqIukHKuRwHX2wXcK7mcbsgFEtbCaWzOw S2ObBUlbTj96iZuxfjjRLcNHQ46M1MiOwSfqVBg5YM80aAhybR0H5mZE4YDIfcUt uVd+gNFgPySLUPMvRUJbEhNC99XDQTf1xiNLB75pNSNc+3b+ZPAzJ1vLmfTzeazd Ecs9Gyf+yZsfZB/KO8N3y1hBnVF3o7r1SEMuYJmYnhEwRfEyseA= =rH1i -----END PGP SIGNATURE----- --MIIlTDOwAbcOUihE--