Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~
Date: 2022-07-11 01:22:32
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, Jul 07, 2022 at 01:56:39PM +0900, Michael Paquier wrote:
> And I have applied that, after noticing that the MinGW was complaining
> because _WIN32_WINNT was not getting set like previously and removing
> _WIN32_WINNT as there is no need for it anymore. The CI has reported
> green for all my tests, so I am rather confident to not have messed up
> something. Now, let's see what the buildfarm members tell. This
> should take a couple of hours..

Since this has been applied, all the Windows members have reported a
green state except for jacana and bowerbird. Based on their
environment, I would not expect any issues though I may be wrong.

Andrew, is something happening on those environments? Is 495ed0e
causing problems?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-07-11 01:31:06 Re: pg15b2: large objects lost on upgrade
Previous Message Michael Paquier 2022-07-11 01:16:44 Re: Allow file inclusion in pg_hba and pg_ident files