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

From Andrew Dunstan
Subject Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB.
Date
Msg-id CAD5tBcKnE3C1hycBYZYtYpNssQR_e+u2=CmDhGRFvDMEg3onRg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB.  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB.
List pgsql-committers


On Sat, Nov 9, 2024 at 11:20 AM Thomas Munro <thomas.munro@gmail.com> wrote:
On Sat, Nov 9, 2024 at 9:30 AM Andrew Dunstan <andrew@dunslane.net> wrote:
> My impression was that this was something we just didn't get around to. I wouldn't have pushed these so close to release if this hadn't been code already tested for a long time in release 16+. Maybe we missed something, but I doubt it.

c5cb8f3b did have a couple more follow-ups: 4517358e and f71007fb.
These fixed initdb when run under a junction point:

https://www.postgresql.org/message-id/4590c37927d7b8ee84f9855d83229018%40postgrespro.ru


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.

cheers

andrew

pgsql-committers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB.
Next
From: Tom Lane
Date:
Subject: pgsql: Release notes for 17.1, 16.5, 15.9, 14.14, 13.17, 12.21.