Re: BUG #15858: could not stat file - over 4GB
Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
From: Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, williamedwinallen@live.com, pgsql-bugs@lists.postgresql.org, Magnus Hagander <magnus@hagander.net>
Date: 2019-06-29T06:19:18Z
Lists: pgsql-bugs, pgsql-hackers
On Sat, Jun 29, 2019 at 4:30 AM Michael Paquier <michael@paquier.xyz> wrote: > > Thanks. Could you attach this patch to the next commit fest? We had > many complaints with the current limitations with large files (pg_dump > syncs its result files, so that breaks on Windows actually if the dump > is larger than 2GB..), and we are going to need to do something. I > find that stuff rather hard to backpatch, but let's see. Done. [1] Regards, Juan José Santamaría Flecha [1] https://commitfest.postgresql.org/23/2189/
Commits
-
Minor cleanup for win32stat.c.
- fcd11329db5b 14.0 landed
- 961e07b8ccb5 14.0 landed
- c94cfb38c32a 14.0 landed
-
plperl.h should #undef fstat along with stat and lstat.
- ed30b1a60dad 14.0 cited
-
Fix our Windows stat() emulation to handle file sizes > 4GB.
- bed90759fcbc 14.0 landed