From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Subject: | Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade |
Date: | 2025-06-05 08:27:06 |
Message-ID: | 40712083-b1a5-4aa6-b35f-d648f7207319@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05.06.25 10:04, Nazir Bilal Yavuz wrote:
> Thomas Munro off-list mentioned that the Windows CI image is actually
> running on Server 2022, even though the task name still refers to
> Server 2019. He also suggested upgrading the compiler from Visual
> Studio 2019 to Visual Studio 2022.
Some of the tasks for the other operating systems name the version, some
don't. We have recently removed the version from the FreeBSD task.
Should we remove the versions from the task name everywhere, to avoid
having further mismatches?
> A PR [1] to upgrade the compiler to VS 2022 is ready in Andres'
> pg-vm-images repository (where the CI images are built). This VS 2022
> image passes all tests for both MinGW [2] and Meson & Ninja [2]. Once
> it's merged, the CI images will automatically start using the VS 2022
> compiler.
Hmm, for the purposes of [0], I think it might be better to keep the
image at VS 2019 for now. Unless there are specific reasons why VS 2022
would be of use now?
[0]:
https://www.postgresql.org/message-id/flat/01a69441-af54-4822-891b-ca28e05b215a%40eisentraut.org
From | Date | Subject | |
---|---|---|---|
Next Message | Nazir Bilal Yavuz | 2025-06-05 08:48:15 | Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade |
Previous Message | Peter Eisentraut | 2025-06-05 08:16:35 | Re: [19] Proposal: function markers to indicate collation/ctype sensitivity |