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 1lBojB-0001Xl-7e for pgsql-bugs@arkaria.postgresql.org; Tue, 16 Feb 2021 01:00:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lBoj9-0007i9-Qb for pgsql-bugs@arkaria.postgresql.org; Tue, 16 Feb 2021 01:00:31 +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 1lBoj9-0007i2-JR for pgsql-bugs@lists.postgresql.org; Tue, 16 Feb 2021 01:00:31 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lBoj2-0003Tr-SD for pgsql-bugs@lists.postgresql.org; Tue, 16 Feb 2021 01:00:31 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 7913110C8; Mon, 15 Feb 2021 20:00:22 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 15 Feb 2021 20:00:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=O2wj/jSNXmlUcL88dHQl+yj5428 lOOTOk+jLqgqXhws=; b=XctgCVGeT3p88wM8nbNTnHf3bSoWTPrdk7qe6ccwQqW e74ZQK3S5yv9sl5nvkdvEOD8oogNGo2R7IPyIV/OgJALHLr7rDNVfmJN0JiE4s9s e7UtfMhi/4R6i1WGu8GQxzOQgVXdd19dLHotqGuZzGwotjmO0Muzw/jOkIeMLdFN LGOLEeExw2epJHPTXLy4DIDeMM/fjomqCqfqAWQP4P3gS4ur+gHpyL9e3ISXmuSn hJTGawMmYNcrflO+o5ymPDoqfA+SecpX1vrsaqvODzTCF7CWk77z0vNZ3PUTOxlE dAx2RnDZx2S0eVKPSf9svwh2ZlnRYouYj83BwnqHlaw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=O2wj/j SNXmlUcL88dHQl+yj5428lOOTOk+jLqgqXhws=; b=Y47vS55u9sde69cs4DNtij Vu9Z97AlsKgOjZKfN5oMLIr5fXNK1mQeSe7jFsDFTdXIJ23ZSEe7BcBkucEIago/ t62PKgs7bz4/IKm3d9Iav1iTNEmeWDbke64M7+RHF2JOPs51FGEQlVyaSsf/mZYS pDuS7zS0N9rsqXtzFBrL/xK1fFSFYqNEIHRiiJ5OdJXDdtloI6DycknyaRbI3zYZ CHjlZ7gORVCt/DHb5yfh/J25Vs1v0eKPhh1CjsopwkosYmYt65+xWGbYy9YHGb08 TYQq5xjiWqxImCODv6BK33dTeNFxElXtDoTMv6fzmLn1cBY36qq033PAf3L+SNZA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrieelgddvlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdefhedmnecujfgurhepfffhvf fukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhi vghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnh epgeejfefftddvhfdtgfelhefgteelgfeuudegueeifeelueekueejhedugfegheefnecu ffhomhgrihhnpehgiidrhihouhdpphhoshhtghhrvghsqhhlrdhorhhgnecukfhppeduud durddutddvrddukedtrddukeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id 4B9B01080066; Mon, 15 Feb 2021 20:00:20 -0500 (EST) Date: Tue, 16 Feb 2021 10:00:17 +0900 From: Michael Paquier To: ivan.salvato@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16866: pg_basebackup Windows Server 2016 Message-ID: References: <16866-623545dc62339188@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="wXtCwG68CVlsb8fK" Content-Disposition: inline In-Reply-To: <16866-623545dc62339188@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --wXtCwG68CVlsb8fK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Feb 15, 2021 at 03:12:10PM +0000, PG Bug reporting form wrote: > Problem: > backup fails when the base.tar.gz achieve di 4 GB with pg_basebackup: error: > could not stat file > "W:\POSTGRES\pg_backup\Base-Backup_2021-02-05_103921/base.tar.gz": Unknown > error. This comes from the fact that Windows stat() is not able to handle files larger than 4GB by design, and the fact that pg_basebackup tries to make durable all the contents of a base backup when it is done streaming something on the target host. I bet that the failure you are seeing is the fsync() part for base.tar.gz. You can bypass that by using --no-sync as option, which would basically emulate what Postgres <= 9.6 is doing. In Postgres 14, the emulation of stat() has been fixed to handle the case of files larger than 4GB: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=bed90759fcbcd72d4d06969eebab81e47326f9a2 This is arguably a bugfix, so we may consider a backpatch in the future, but knowing how invasive the fix is we are still in a phase where we want to have some dust settle on this change and Windows has its own way to do weird things all the time. IMO, It may be better to revisit that a couple of months after 14 is released so as there is some feedback from the field with this change. -- Michael --wXtCwG68CVlsb8fK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmArGSEACgkQnvQgOdby QH0mmQ//Te+YlS1up1FpGnFHGH0/WY16MP2m4LeIuyEog1BMikUnMSxoLXCQzAxP sqXbev9Zi5DIvlnml0DPdkvEEo79iBw/0CJ2jtqcNppMQpfx6iAgODi7CL47qLQ4 qpOhAbFhz2orh8H9TLyhoKhY+YMTCLO1Yes9bRGJ8i92NpWuZ9QmdMKQuruPL5J5 VvQuhAD9o5wqDIg8nvxTHZuILhbBufVmdhmPzqoUkTXqFs8Jdi70OPjBukJjtVdE mEA+UpUB1LXgIG0hhzmD4Y4o8nfqr9DB4HhhZLbPaJOy7l6p3FcnB3MsegvMtlMV DaRf1OBifHJC0NMYWtybxR9SKQ7ZtmIHHHTTAUgtYo6Rkq2/wiUZXSQCGNRZCMZv 8tP0EFLGmFd9KXMVsM7YbagSNbKyFAdhCXtng5oMa8hCS5nKeb6VDfjEW9AZOO5H FRZKVU5gHzCikSVgUTasHAkuVxTAUtCdSAtiHqAfOIhQAbVWTpDa2zWHjFm4T8Iv x6zpsM89l0+LT9oNUQmxd4Ea6amuK+FEyRL6vDwNYQSx8xTI8+D8jfSBew/HcaDV juXwj6HgCM5fUuWHmGKRIuQ18iPAAw6tKr049pu1t56etQb0VlIl+AumvCNB784d qfN/FmyhMFYz8GaswZ5wyCBE//CiCjhjzBI9bax69uBcexQuJUk= =DFsY -----END PGP SIGNATURE----- --wXtCwG68CVlsb8fK--