Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB. - Mailing list pgsql-committers

From Thomas Munro
Subject Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB.
Date
Msg-id CA+hUKGKWG0L8DJA+=Rs_cT27wEQUg-LGM1WWaBYx+74GGK8s6A@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB.  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-committers
On Sun, Nov 10, 2024 at 8:12 PM Andrew Dunstan <andrew@dunslane.net> wrote:
> Oh, ouch. I guess it's too late to add those for this release. Still, an initdb failure is not as bad as a pg_rewind
failure,IMNSHO. 

Yeah, I don't think it's all that bad.  It seems both unlikely
(certain kinds of junction points with no intermediate directories, or
chains of junction points), and easy to work around once you get the
idea by experimentation (probably: add subdir, or tell initdb the real
target path directly, or move into place).

In hindsight I should have posted that observation onto the -hackers
thread where people able to test on Windows would have been more
likely to act, not buried here in -committers (and I didn't want to
commit blind to pre-CI branches in a hurry myself).  Sorry about that.



pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix broken collate.icu.utf8 test in v12 branch.
Next
From: Thomas Munro
Date:
Subject: pgsql: jit: Remove obsolete LLVM version guard.