Re: copy command bug - Mailing list pgsql-bugs

From Tom Lane
Subject Re: copy command bug
Date
Msg-id 33819.1602877138@sss.pgh.pa.us
Whole thread Raw
In response to copy command bug  (Mary LaClair <mary@caliper.com>)
List pgsql-bugs
Mary LaClair <mary@caliper.com> writes:
> The copy command fails to load a large csv file (>2GB) with a "Could not
> stat file" error.  This occurs on Windows with all versions since 10.7.
> It happens because fstat() on Windows fails with large csv files.

Yeah, that's a well-known problem.  It has been fixed in HEAD, cf
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=bed90759fcbcd72d4d06969eebab81e47326f9a2
and some follow-up patches.  But unfortunately that's too invasive
for a back-patch, since it causes an ABI break for everything using
"struct stat".  I don't think we'll be terribly interested in hacking
things to fix individual call sites instead, though.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Mary LaClair
Date:
Subject: copy command bug
Next
From: PG Bug reporting form
Date:
Subject: BUG #16677: pgcrypto.pgp_key_id() thinks that a PGP message containing multiple packets is a full keyring.