Re: stat() on Windows might cause error if target file is largerthan 4GB
От | Alvaro Herrera |
---|---|
Тема | Re: stat() on Windows might cause error if target file is largerthan 4GB |
Дата | |
Msg-id | 20200509004920.GA4395@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: stat() on Windows might cause error if target file is larger than 4GB (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: stat() on Windows might cause error if target file is larger than 4GB
|
Список | 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 по дате отправления: