| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | 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-06 05:30:33 |
| Message-ID: | 898d87dc-5e58-4fbc-8307-c6f226b44e67@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2025-06-06 05:37:36 | Re: Avoid orphaned objects dependencies, take 3 |
| Previous Message | Amit Kapila | 2025-06-06 05:19:13 | Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly |