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 1iXSDA-0007Ky-P8 for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Nov 2019 15:48:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iXSD8-00064J-P4 for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Nov 2019 15:48:06 +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 1iXSD8-000646-Dn for pgsql-bugs@lists.postgresql.org; Wed, 20 Nov 2019 15:48:06 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iXSD5-0001v4-Gv for pgsql-bugs@lists.postgresql.org; Wed, 20 Nov 2019 15:48:04 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xAKFlfN7003360; Wed, 20 Nov 2019 10:47:42 -0500 From: Tom Lane To: leiyanliang@highgo.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: =?utf-8?q?BUG_=2316127=3A_PostgreSQL_12=2E1_on_Windows_2008_R2_copy_table_from_=E2=80=98large_2GB_csv=E2=80=99report_=E2=80=9CUnknown_error=E2=80=9D?= In-reply-to: <16127-cd8faadee42e85d5@postgresql.org> References: <16127-cd8faadee42e85d5@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 20 Nov 2019 12:42:38 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3357.1574264861.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 20 Nov 2019 10:47:41 -0500 Message-ID: <3358.1574264861@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > postgres=3D# copy github_events from 'd:\large_events.csv' csv; > ERROR: could not stat file "d:\large_events.csv": Unknown error = > ----->>>Please note this error!!! > 1. d:\large_events.csv this file is large 2GB Given that, I wonder if this isn't the same issue being worked on over here: https://www.postgresql.org/message-id/flat/15858-9572469fd3b73263@postgres= ql.org https://commitfest.postgresql.org/25/2189/ If you could help review/test that patch, it would make it more likely to get fixed soon. regards, tom lane