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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, williamedwinallen(at)live(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: BUG #15858: could not stat file - over 4GB
Date: 2019-06-29 02:30:31
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs pgsql-hackers

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.

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2019-06-29 05:09:42 Re: BUG #15677: Crash while deleting from partitioned table
Previous Message Paul Ramsey 2019-06-28 22:15:16 Re: Re: Querying foreign table with SP-GiST index results in “ERROR: cache lookup failed for type 0”

Browse pgsql-hackers by date

  From Date Subject
Next Message Jesse Zhang 2019-06-29 05:11:11 Re: C testing for Postgres
Previous Message Michael Paquier 2019-06-29 02:24:49 Re: cleanup & refactoring on reindexdb.c