Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade - Mailing list pgsql-hackers

From Nazir Bilal Yavuz
Subject Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade
Date
Msg-id CAN55FZ2Rr9RpdrGk4V3NugqAzQd3_L=+qyT-6401KP9zSt83VA@mail.gmail.com
Whole thread Raw
In response to Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
Hi,

On Fri, 6 Jun 2025 at 08:30, Peter Eisentraut <peter@eisentraut.org> wrote:
>
> On 05.06.25 12:42, Thomas Munro wrote:
> > I think on your C11 thread I might have been confused about that,
> > since there was an implication that 2019 might support <stdatomic.h>,
> > but it looks like 2019 added language stuff while 2022 added the
> > library stuff.  But yeah, given your proposal that MSVC 2019 should be
> > our new minimum target on that platform, I wonder if we should have
> > both available in CI somehow...
>
> It would be useful to have a leading and a trailing edge CI system for
> every OS family.  For example, say, Ubuntu 25.04 and RHEL 7, and VS 201x
> and VS 202y.  Because as we are seeing here, sometimes you're more
> concerned about breaking the old one, and sometimes you're more
> interested in using a feature on the new one.  Maybe one of the two
> could be manually triggered to save on resources.

I think that is pretty doable. First we need to decide on a list of OS
families, though.

-- 
Regards,
Nazir Bilal Yavuz
Microsoft



pgsql-hackers by date:

Previous
From: Jim Jones
Date:
Subject: Re: Add XMLNamespaces to XMLElement
Next
From: Amit Kapila
Date:
Subject: Re: Replication slot is not able to sync up