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-07 04:56:39
Message-ID: YsZnhwERsDv/
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, Jul 07, 2022 at 09:11:57AM +0900, Michael Paquier wrote:
> Okay, thanks for confirming. I think that I'll give it a try today
> then, my schedule would fit nicely with the buildfarm monitoring.

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..

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-07-07 05:04:13 Re: pg_upgrade (12->14) fails on aggregate
Previous Message Andres Freund 2022-07-07 04:36:56 Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower