Re: copy command bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mary LaClair <mary(at)caliper(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: copy command bug
Date: 2020-10-16 19:38:58
Message-ID: 33819.1602877138@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Mary LaClair <mary(at)caliper(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-10-16 23:52:26 BUG #16677: pgcrypto.pgp_key_id() thinks that a PGP message containing multiple packets is a full keyring.
Previous Message Mary LaClair 2020-10-16 19:16:52 copy command bug