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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB.
Date: 2024-11-09 00:49:40
Message-ID: CA+hUKGLa_nc36wAAvAeqz06_UeKs-jKi++gYCANxM6BiOghyxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, Nov 9, 2024 at 9:30 AM Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2024-11-10 07:12:19 Re: pgsql: Fix our Windows stat() emulation to handle file sizes > 4GB.
Previous Message Nathan Bossart 2024-11-08 22:14:05 pgsql: Fix sign-compare warnings in pg_iovec.h.