From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mary LaClair <mary@caliper.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: copy command bug
Date: Fri, 16 Oct 2020 15:38:58 -0400
Message-ID: <33819.1602877138@sss.pgh.pa.us> (raw)
In-Reply-To: <e831d360-c991-3078-01e6-47533df4c179@caliper.com>
References: <e831d360-c991-3078-01e6-47533df4c179@caliper.com>
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=bed90759fcbcd72d4d06969eebab81e47...
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, mary@caliper.com, pgsql-bugs@lists.postgresql.org
Subject: Re: copy command bug
In-Reply-To: <33819.1602877138@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox