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

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: 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 16:07:14
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs pgsql-hackers

On Wed, Jun 19, 2019 at 3:26 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> 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:

Going through this discussion it is not clear to me if there was a
consensus about the shape of an acceptable patch. Would something like
the attached be suitable?


Juan José Santamaría Flecha

Attachment Content-Type Size
0001-support-for-large-files-on-Win32.patch application/octet-stream 2.3 KB

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Gierth 2019-06-19 17:06:26 Re: BUG #15855: Using 'nextval' inside INSERT RULE in case of bulk data insertion.
Previous Message Albrecht Scheidig 2019-06-19 15:47:59 XSS Bug in Query View

Browse pgsql-hackers by date

  From Date Subject
Next Message Dagfinn Ilmari Mannsåker 2019-06-19 17:04:27 Re: Remove one last occurrence of "replication slave" in comments
Previous Message Thom Brown 2019-06-19 16:06:51 Re: SQL/JSON path issues/questions