From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: Update Windows CI Task Names: Server 2022 + VS 2022 Upgrade |
Date: | 2025-06-10 07:12:58 |
Message-ID: | CAN55FZ2Rr9RpdrGk4V3NugqAzQd3_L=+qyT-6401KP9zSt83VA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Fri, 6 Jun 2025 at 08:30, Peter Eisentraut <peter(at)eisentraut(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2025-06-10 07:15:06 | Re: Replication slot is not able to sync up |
Previous Message | Jim Jones | 2025-06-10 07:10:51 | Re: Add XMLNamespaces to XMLElement |