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 1iXShP-000050-Jx for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Nov 2019 16:19:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iXShN-0002hl-Rs for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Nov 2019 16:19:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iXShN-0002hc-Fk for pgsql-bugs@lists.postgresql.org; Wed, 20 Nov 2019 16:19:21 +0000 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iXShG-0005M4-0x for pgsql-bugs@lists.postgresql.org; Wed, 20 Nov 2019 16:19:20 +0000 Received: by mail-wr1-x441.google.com with SMTP id i12so509292wro.5 for ; Wed, 20 Nov 2019 08:19:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=SXcZkn/Sa/CExXlBPi6ZuOSujfGXq5mRYMXYOeOpbJA=; b=im7ZUIzzq31Al0B7iJH9RRxNLeAsNZEC6xC4KnHSiR4PmF5b4lFrRseJBkgPLIIF96 6yB0KwsYN3R25Eof56Hgg5fmCC5+Xrp+CFnc4XKocfuVy/NNv91e/3uHCdnpuZSLDH0G IjT+ORF0C+YSY0Vm/fNcAxbS9ytZyWxoen9r0DF+cISM9HSrswTJzVoGLEoaRoOG0zdE GR3FAJr3gTdpB00+NGHLcVBBgfdfEHUDMSBWDTKjfoLkTNQr/1i5rdtLZI/GSUvmeQv+ dgvHr3Q01esHyZVzOCZ+1PB/K+WNKOUCDUdzj7HDOCOXEtbgVGDzcXxcrQWy7QCljvKk LE+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=SXcZkn/Sa/CExXlBPi6ZuOSujfGXq5mRYMXYOeOpbJA=; b=TKoO7WRfHl0yTSzovWZphlkucxSM3UZWMxaEUMKKI9/K3lgJuockjOgCdIvcVFw+rU hquVsxqHP9zV4jG7AvZr4AMRoFlJ83M5e/9sKZwmVUoAaiczjqGtuUMFZLXZsOQGqsd6 x6LtnLvLaoy62Vg7LoF9osqpL1lOyo0HpeCbPiO4jucwzak/UAYqFYpEsyVrV+waU+Yk SBT0IS1oZwgeujwlumZC6Q7Bu1M2Z4mprw6c474dDKBUq1NNRJC8+GpwtsTwxoLkbFpx mkhPvMWZ94wm2VS70fsBWarhCuEEKlmgWbHRh7quDoNF4JdXgFBMq6f8qvrl5GcDg8X4 bEWA== X-Gm-Message-State: APjAAAVjsHSTViNCnWzNHFx+MpdmdxLK+nAEv7fTLUMggH/8crubAfgU EMgAAYg4vQrMZEas0SAZxY+wLnenr6Q= X-Google-Smtp-Source: APXvYqwX6z7nzcC4oYWxhXNbZ13ZfvBM7gbziPENd65cf3vL/aOwhZsoy2GarSwVx1XnQ4UUsYxyDw== X-Received: by 2002:adf:fec5:: with SMTP id q5mr4452460wrs.293.1574266752777; Wed, 20 Nov 2019 08:19:12 -0800 (PST) Received: from localhost (ip-86-49-253-92.net.upcbroadband.cz. [86.49.253.92]) by smtp.gmail.com with ESMTPSA id n1sm32484208wrr.24.2019.11.20.08.19.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Nov 2019 08:19:10 -0800 (PST) Date: Wed, 20 Nov 2019 17:19:09 +0100 From: Tomas Vondra To: "leiyanliang@highgo.com" Cc: "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #16127: PostgreSQL 12.1 on Windows 2008 =?utf-8?Q?R2copy_?= =?utf-8?B?dGFibGUgZnJvbSDigJhsYXJnZSAyR0IgY3N24oCZcmVwb3J0IOKAnFVua25v?= =?utf-8?B?d24gZXJyb3LigJ0=?= Message-ID: <20191120161909.edfjorf7rnvrox6q@development> References: <16127-cd8faadee42e85d5@postgresql.org> <20191120132159.7xlgs2sl3ggoeiel@development> <201911202141482799261@highgo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201911202141482799261@highgo.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Nov 20, 2019 at 09:42:49PM +0800, leiyanliang@highgo.com wrote: >Thank you for reply. > >I do not think the root cause of this problem is about privilege,and this windows machine is my test machine, only I have access to this machine. > >I think this problem is a bug,there are two evidences: > >The first evidence : > >postgres=# select version(); > version >------------------------------------------------------------ > PostgreSQL 12.1, compiled by Visual C++ build 1914, 64-bit >(1 行记录) > > >时间:0.280 ms >postgres=# >postgres=# >postgres=# copy github_events from 'd:\events.csv' csv; ----->>> d:\events.csv( about 316,302,020 Bytes) can copy succussfully!! >COPY 126245 >时间:19574.819 ms (00:19.575) >postgres=# \q > Ah, I haven't noticed the information about file size in the first post, as it was buried at the very end :-( In that case, I think Tom is right it's likely the same issue as [1], although that starts with a report about issues with 4GB. Maybe that's due to using different windows version 2008 R2 vs. 2012 R2, though. It'd be good if you could test the latest patch [2] in that thread. You'll need to build PostgreSQL on Windows, though - I don't have much experience with that, but there are wiki pages about doing that either using Visual Studio [3] or mingw [4]. regards [1] https://www.postgresql.org/message-id/15858-9572469fd3b73263%40postgresql.org [2] https://www.postgresql.org/message-id/attachment/103789/0001-WIP-support-for-large-files-on-Win32-v4.patch [3] https://wiki.postgresql.org/wiki/Working_With_VisualStudio [4] https://wiki.postgresql.org/wiki/Building_With_MinGW -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services