Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdPMd-0005TL-81 for pgsql-bugs@arkaria.postgresql.org; Wed, 19 Jun 2019 01:26:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hdPMb-0005KT-Qz for pgsql-bugs@arkaria.postgresql.org; Wed, 19 Jun 2019 01:26:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdPMb-0005KM-G4 for pgsql-bugs@lists.postgresql.org; Wed, 19 Jun 2019 01:26:13 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hdPMY-0002xZ-HO for pgsql-bugs@lists.postgresql.org; Wed, 19 Jun 2019 01:26:12 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 492A2209B5; Tue, 18 Jun 2019 21:26:09 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 18 Jun 2019 21:26:09 -0400 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=fm2; bh=vmFqQ3yZ1tOHt2h4qllybVAqTZm AY6K0ozvTaGd6z4E=; b=jHAz0OotGjJFJ5SpCJ+wJoakd+K12/+NSr+frpzt+v4 r+YJRowRcrl2rylNO1H+Crbu5RzffMlSIJ3p7c6PItmztaYIlsVG+zn6LFuYy1Vg GLoWlgTbgIGed1jvbRmpmVfsDyBQv4qOVi8nQW5qF+KNbLX2w8Zbc0MWjtuvQww7 Wr1ZaLfJV5VKi0nbsLIwDiHPQa5n9ehC7RSQWBZRMik6AMRpZ1BTqUFshaZ8PmeA 1OzNCUbgBlVzJq+lbZh5oCfpMbIrDeL3OHhGhWcduEGwvskOWsEKrwSjPQ2aNbnE uPaO8KFELm9QavU/NVDfRo+7qZggaP3vKylOn5H6qJQ== 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=fm3; bh=vmFqQ3 yZ1tOHt2h4qllybVAqTZmAY6K0ozvTaGd6z4E=; b=BRwLM7F341DTd/47ZCRofA 0Um5uZyz23xfgt5Y6BR7089p7J2rbK2V0KUd1rK7s9Om0PGvFtwZvEHuUY1b9hh+ QI7o4jwNWlAHw+C+jYRU10zJ030MId/Jsr/Y9zEqOlJDLyz8rw5ZmlhNivd3c45X ZKM6qJ/yLH3nNhvOoqXsU2/U709USpL70ZuAhH/ZcLeESv/NJUxNQH6fk5Ho9Zaf MjPWTmX3ZUAhuzdvgxJjTOMjw8jMDdCRc1UrZGWrw6nrNmLVxaSO6A5uRZR6XUjj eS2K2mUiaitLPqHLc9Hi+2UKoiEYQgh8BzSfGqqBKcK9rf0f4FYHWz3Ip/xKQ3xA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrtddugdeghecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdefhedmnecujfgurhepfffhvf fukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhi vghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuffhomhgrihhnpehpoh hsthhgrhgvshhqlhdrohhrghenucfkphepudduuddruddtvddrudektddrudekheenucfr rghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihiienuc evlhhushhtvghrufhiiigvpedt 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 A1C6B80059; Tue, 18 Jun 2019 21:26:07 -0400 (EDT) Date: Wed, 19 Jun 2019 10:26:04 +0900 From: Michael Paquier To: williamedwinallen@live.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15858: could not stat file - over 4GB Message-ID: <20190619012604.GC2135@paquier.xyz> References: <15858-9572469fd3b73263@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="1SQmhf2mF2YjsYvc" Content-Disposition: inline In-Reply-To: <15858-9572469fd3b73263@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --1SQmhf2mF2YjsYvc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 18, 2019 at 10:02:53AM +0000, PG Bug reporting form wrote: > Issue using copy from command for files over 4GB. >=20 > ERROR: could not stat file "E:\file.txt": Unknown error > SQL state: XX000 Windows is known for having limitations in its former implementations of stat(), and the various _stat structures they use make actually that much harder from a compatibility point of view: https://www.postgresql.org/message-id/1803D792815FC24D871C00D17AE95905CF509= 9@g01jpexmbkw24 Nobody has actually dug enough into this set of issues to get a patch out of the ground, which basically requires more tweaks that one may think at first sight (look at pgwin32_safestat() in src/port/dirmod.c for example). -- Michael --1SQmhf2mF2YjsYvc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl0JjywACgkQnvQgOdby QH2jjRAAl1HuYZvEzdPK1BUd088Go+6TMtFLEEaH1iJ278siJLwth7Qm3xggtZiC Yht/h/mvcqWU5FJrPC4QpI/BWrV7umkBYvBfF8ATnCcKmzHcciTIKs/D622LynOi C8cZ6i/aQEvDntc8Cxr7bN2Y7us3pg1YE4UQLTwIpoZFhqc0gtmBvuMVrAf5qgC0 TtbSEBjQQprDpQmxbrItvAtDk+LD/VtfFE2EJWHEwlgzFMiJrU3F+nbH+rKKlqsp CByMFRAjnBCLYH98H4qxzsG8ztITsKtq+cxhkjtORBx6l9NMZBwz1Bv+uEDlYL2q 3jAHu2FpmgUVnr+9n86Ilv3kPlkmFdwGL9quUlncnXza3qPaLRLcVSTrSW8Dtcb/ FUNt+l5I74sahSZuiRxJvOqQLU9ojpUe9jjw7Pcn2hprQris5qs0454q2+q1oIAG X0ZfoKEmcYL31r8i+y9LzgqOT1275tML0/a0tEmBKTekkonEbvGdO+Tacbbswlut TT9iBR7W32a0TaGhj6GdRel2oAn2JLAuOTF0e/9RCm2KYE9DFD8YJ/QRbcYMPfkh sZ/GpVe/Vn1FULpcFL7+GrENty/udPCxhjBxxdtEdIHCvktUWtuNhh5wln8Ti8JF oejsBXAHcl3dFu3w90oalsYb4eEKCeptNFUXbDNSpTCnmYdvJoI= =ylhX -----END PGP SIGNATURE----- --1SQmhf2mF2YjsYvc--