Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~ - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~
Date
Msg-id CA+hUKGL1p7BHdZc_GEBYkLarPzFEAYKd_HXA_NJ_ct4dJCD-iw@mail.gmail.com
Whole thread Raw
In response to Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~
List pgsql-hackers
On Wed, Jul 6, 2022 at 7:28 PM Michael Paquier <michael@paquier.xyz> wrote:
> On Thu, Jun 16, 2022 at 03:14:16PM +0900, Michael Paquier wrote:
> > Actually, this can go with the bump of MIN_WINNT as it uses one of the
> > IsWindows*OrGreater() macros as a runtime check.  And there are two
> > more places in pg_ctl.c that can be similarly cleaned up.
> >
> > It is possible that I have missed some spots, of course.
>
> It does not seem to be the case on a second look.  The buildfarm
> animals running Windows are made of:
> - hamerkop, Windows server 2016 (based on Win10 AFAIK)
> - drongo, Windows server 2019
> - bowerbird, Windows 10 pro
> - jacana, Windows 10
> - fairywren, Msys server 2019
> - bichir, Ubuntu/Windows 10 mix
>
> Now that v16 is open for business, any objections to move on with this
> patch and bump MIN_WINNT to 0x0A00 on HEAD?  There are follow-up items
> for large pages and more.

+1 for proceeding.  This will hopefully unblock a few things, and it's
good to update our claims to match the reality of what we are actually
testing and able to debug.

The build farm also has frogmouth and currawong, 32 bit systems
running Windows XP, but they are only testing REL_10_STABLE so I
assume Andrew will decommission them in November.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: EINTR in ftruncate()
Next
From: Tom Lane
Date:
Subject: Re: automatically generating node support functions