Re: BUG #15858: could not stat file - over 4GB - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #15858: could not stat file - over 4GB
Date
Msg-id 20190629023031.GD2191@paquier.xyz
Whole thread Raw
In response to Re: BUG #15858: could not stat file - over 4GB  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
Responses Re: BUG #15858: could not stat file - over 4GB
List pgsql-bugs
On Fri, Jun 28, 2019 at 11:34:38PM +0200, Juan José Santamaría Flecha wrote:
> I wanted to make a quick test on the previous patch. So let me state
> what have I tested and what I have not: it builds and pass tests in
> Windows and Cygwin, but I have not setup a MinGW environment.

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.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Paul Ramsey
Date:
Subject: Re: Re: Querying foreign table with SP-GiST index results in “ERROR: cache lookup failed for type 0”
Next
From: Amit Langote
Date:
Subject: Re: BUG #15677: Crash while deleting from partitioned table