Re: BUG #15858: could not stat file - over 4GB

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: williamedwinallen(at)live(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15858: could not stat file - over 4GB
Date: 2019-06-19 01:26:04
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs pgsql-hackers

On Tue, Jun 18, 2019 at 10:02:53AM +0000, PG Bug reporting form wrote:
> Issue using copy from command for files over 4GB.
> ERROR: could not stat file "E:\file.txt": Unknown error
> SQL state: XX000

Windows is known for having limitations in its former implementations
of stat(), and the various _stat structures they use make actually
that much harder from a compatibility point of view:

Nobody has actually dug enough into this set of issues to get a patch
out of the ground, which basically requires more tweaks that one may
think at first sight (look at pgwin32_safestat() in src/port/dirmod.c
for example).

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-06-19 13:56:21 BUG #15860: Postgresql service does not start when the pg_hba.conf is changed
Previous Message Michael Paquier 2019-06-19 01:22:09 Re: BUG #15859: Postgres 11 repository is missing extensions

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-06-19 02:04:16 Re: nbtdesc.c and nbtpage.c are inconsistent with XLOG_BTREE_META_CLEANUP (11~)
Previous Message Thomas Munro 2019-06-19 01:07:23 Tweaking DSM and DSA limits