Re: stat() on Windows might cause error if target file is largerthan 4GB - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: stat() on Windows might cause error if target file is largerthan 4GB
Date
Msg-id 20200509004920.GA4395@alvherre.pgsql
Whole thread Raw
In response to Re: stat() on Windows might cause error if target file is larger than 4GB  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: stat() on Windows might cause error if target file is larger than 4GB  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
List pgsql-hackers
On 2018-Sep-13, Tom Lane wrote:

> What I was vaguely imagining is that win32_port.h could #include
> whichever Windows header defines these functions and structs, and
> then do
> 
> #define stat __stat64
> 
> static inline ... __stat64(...) { return _stat64(...); }
> 
> What would need testing is whether the #define has nasty side-effects
> even if we've already included the system header.  I don't think it'd
> hurt, eg, local variables named "stat"; though people might be surprised
> when examining things in a debugger.

Did anybody test this idea?  It seems we let this problem slip unfixed,
which means Windows users cannot use pg_dump -Fd (incl. parallel dump)
when output files are large.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Include sequence relation support in logical replication
Next
From: Melanie Plageman
Date:
Subject: Re: Avoiding hash join batch explosions with extreme skew and weird stats