Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1frVvf-0000If-67 for pgsql-bugs@arkaria.postgresql.org; Sun, 19 Aug 2018 22:12:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1frVvd-0005JH-LP for pgsql-bugs@arkaria.postgresql.org; Sun, 19 Aug 2018 22:12:09 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1frVvb-0005J2-TT for pgsql-bugs@lists.postgresql.org; Sun, 19 Aug 2018 22:12:09 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1frVvX-000688-Qf for pgsql-bugs@lists.postgresql.org; Sun, 19 Aug 2018 22:12:06 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7FF15211A9; Sun, 19 Aug 2018 18:12:02 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 19 Aug 2018 18:12:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=Jk0ZV7L5paX0R+eQZAqPaI5p3Ri53yvt7TDopeszHN4=; b=bO4xZdgg qdVJAJhh15BaEvXlm6aW2cPVFvxXVl6cJvFlj2fM0ucPoVRLtEQ1N6z0cddWTZts RrKsHAiMtyXnV8HcQrRBU4chWgTfzXHERh+E432UkcafYIu0nnzAMLNIgiH1e91u UIykqxqF2mEaqCmGQRLC1stqJz6ZZ/NZ+lOikcD17CikQ3V0mWzGU2mroJAGhXbN Q81aRVc/FNXznUDK8TOc8WwY8SOE9dBRxUVbjJaytuZQhiGXRGS2xs3UxcghuEpg WouecoUUpcVPh2rGnmitbtw7gRefCdk7b1dV2xeafUItWIpeo3Eog1x3oC9lJzTG FXpuBhqCYA7zZQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=Jk0ZV7L5paX0R+eQZAqPaI5p3Ri53 yvt7TDopeszHN4=; b=OpU+Kt0kOeOnk6kDJjGpOIFGUdXd0DIKTPwk4vg1j5NjM TbgvozrmUlGWLcX/JjHxnGMi9NqPevgkvlWIdzy9jIV/D5UO4lTXGxBtKe4RwsMr IWgVCZXDPYa9MEtlKeeCsTQNqedERVqHrml8ESEBhvMYjU/PIaZpwPMPSRfnbZeW AHIr/WK58m5ttxHpV59SCremZwjFu1m8iI6ka0+efVi7Z0z3kI+ITaQgI/78gsJT kI/Ha7z26m/yP5cNST79iUn/YtMa+nCjeRP4mjPKa7bmp4CaakXE31Y8cgqgXW1N mcXqSIKpvJ/5rWZWiBeDl88w6N08X3MCvgeKsKSPQ== X-ME-Proxy: X-ME-Sender: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 91C2FE425A; Sun, 19 Aug 2018 18:12:00 -0400 (EDT) Date: Mon, 20 Aug 2018 07:11:57 +0900 From: Michael Paquier To: Tom Lane Cc: Mark Lai , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15333: pg_dump error on large table -- "pg_dump: could not stat file...Unknown error" Message-ID: <20180819221157.GC1785@paquier.xyz> References: <153442391458.1505.9181095584291689853@wrigleys.postgresql.org> <13611.1534433145@sss.pgh.pa.us> <5632.1534517591@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Bu8it7iiRSEf40bY" Content-Disposition: inline In-Reply-To: <5632.1534517591@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Bu8it7iiRSEf40bY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 17, 2018 at 10:53:11AM -0400, Tom Lane wrote: > Mark Lai writes: >> I ran the dump on the large table with no jobs flag and got the same err= or. >> ... >> The dump was successful on a small table. >=20 > Weird indeed. Can any Windows developers reproduce this and poke into it? >=20 > I have a sneaking suspicion that this is related to Windows' known issues > with concurrently-opened files, but it's pretty hard to see why there > would be a dependency on the size of the file. When it comes to pg_dump, the error message reported seems to come from src/common/file_utils.c, in walkdir when processing links. On Windows we map lstat() to stat(), which is itself pgwin32_safestat(). If you use pg_dump --no-sync, the error could be bypassed but that's hardly a fix. That could be a failure on GetFileAttributeEx(). Which file system are you using? -- Michael --Bu8it7iiRSEf40bY Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlt56y0ACgkQnvQgOdby QH31Cw/9F8LpqNdCL4a5qFTCgDXPwRB7kBL46WG0a1NrnMre9gmP/eGvc7PRrm/g +VM4HbJR6L6k9NXo7DnpahTU93dC7PxkqNmhFZSFtGtq6IlAh+CvJUleVmKIYKtO 4pP+Tc6c3dwW2ExYTiMW1f6jMJBTAR/9KSIWqq+sa3bD0DGPpvmeY8eGVwBc1Kdi Jn20i5+J7Ho8yxcNimDmxRSXic4lK7LAf7sjg/XOh+fso2bOfy/hKSfk61vAvN8Y IiJhyq7jdaBAElwskLVb/TMMfbPL+UX2Ks8u3/ASCAnmJcncs/9R5ykgHeC/9784 MsSFyJkHGa7i4VthLVLAzJitFi9QMB6AAx7lzLjv/FlCImxB4Mjjfj/RfRmgbwvl NUQW49D/5s01BGUDx+06sOMEFbRt1JttsaTOXgPyWuzxU6kFD+GEwWQjKt4vE3rP BocYH+9+eZnpHAU0qJys+G/9vSezB81nnw1exYHSedrmMi2paNjDSxmzNLFbQvxu xq3dHpBlFOLnkg5BwtzOzdUUKvApZ9+Tw6d0tFFqKZxRwWb5cgjtUDheejLLsdHE SvXXtftHReQAch0GH83zywfBPs0yi8xaOOeCuuQtzzX3dxxUM0VktlHw5Kjhru5P hA+ThCQBUgMiEgypA3ewQFvspvV6vxDCr5O+xJItzUa5lpLXm9o= =zMaq -----END PGP SIGNATURE----- --Bu8it7iiRSEf40bY--