From: Michael Paquier <michael@paquier.xyz>
To: Bruce Momjian <bruce@momjian.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 16 draft release notes ready
Date: Sun, 23 Jul 2023 20:19:55 +0900
Message-ID: <ZL0M28/L+grYR8o7@paquier.xyz> (raw)
In-Reply-To: <ZKSP1zSl2VOf+F5m@momjian.us>
References: <ZGaPa7M3gc2THeDJ@momjian.us>
<ZKO8qTCRaMIgwznX@paquier.xyz>
<ZKSP1zSl2VOf+F5m@momjian.us>
On Tue, Jul 04, 2023 at 05:32:07PM -0400, Bruce Momjian wrote:
> On Tue, Jul 4, 2023 at 03:31:05PM +0900, Michael Paquier wrote:
>> On Thu, May 18, 2023 at 04:49:47PM -0400, Bruce Momjian wrote:
>> Sawada-san has mentioned on twitter that fdd8937 is not mentioned in
>> the release notes, and it seems to me that he is right. This is
>> described as a bug in the commit log, but it did not get backpatched
>> because of the lack of complaints. Also, because we've removed
>> support for anything older than Windows 10 in PG16, this change very
>> easy to do.
>
> I did review this and wasn't sure exactly what I would describe. It is
> saying huge pages will now work on some versions of Windows 10 but
> didn't before?
Windows 10 has always used a forced automated rolling upgrade process,
so there are not many versions older than 1703, I suppose. I don't
know if large pages were working before 1703 where
FILE_MAP_LARGE_PAGES has been introduced, and I have never been able
to test that. Honestly, I don't think that we need to be picky about
the version mentioned, as per the forced upgrade process done by
Microsoft.
So, my preference would be to keep it simple and add an item like "Fix
huge pages on Windows 10 and newer versions", with as potential
subnote "The backend sets a flag named FILE_MAP_LARGE_PAGES to allow
huge pages", though this is not really mandatory to go down to this
level of internals, either.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers@postgresql.org
Cc: michael@paquier.xyz, bruce@momjian.us
Subject: Re: PG 16 draft release notes ready
In-Reply-To: <ZL0M28/L+grYR8o7@paquier.xyz>
References: <ZGaPa7M3gc2THeDJ@momjian.us> <ZKO8qTCRaMIgwznX@paquier.xyz> <ZKSP1zSl2VOf+F5m@momjian.us> <ZL0M28/L+grYR8o7@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox