Hi,
On Thu, 5 Jun 2025 at 11:27, Peter Eisentraut <peter@eisentraut.org> wrote:
>
> 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?
I think one of the biggest advantages of having a version in the task
name is immediately seeing if something is updated (without checking
-hackers or sysinfo). However, most of the information is already
available in the sysinfo in the task and since we removed the version
from FreeBSD; I think we can remove it from all of the tasks.
> > 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?
Thomas was thinking of trying some new APIs which are available in the
VS 2022, he may answer this better.
--
Regards,
Nazir Bilal Yavuz
Microsoft
