VS 2026 support on old branches

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: VS 2026 support on old branches
Date: 2026-07-07 20:30:55
Message-ID: CAD5tBc+nFmaqqCaxDdQUMtOmtTb3nrvXn2TiVjLQyy0FV1BcUQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greetings,

Peter E pinged me recently about the need to upgrade drongo because he was
planning to commit some stuff that would break on VS 2019. I chose to
update it to VS2026, and this promptly broke on the old branches. I've
hacked its config for now to use the older setup for 14 and 15, but that's
not very principled - and buildfarm members are supposed to use the same
compiler for all branches. If anyone wants to set up a buildfarm animal now
they will have to choose between using an older compiler (VS2022) and not
supporting all the live branches. So here's a patch (which I have tested)
that adds support for VS2026 on those old branches, pretty much in line
with what we've done before. With any luck, Microsoft won't come out with
another release until after the date our release 15 goes EOL, at which
point we will be done with this kabuki dance.

cheers

andrew

Attachment Content-Type Size
0001-Add-support-for-Visual-Studio-2026-in-build-scripts.patch text/x-patch 9.0 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2026-07-07 21:00:27 Re: allow spread checkpoints when changing checksums online
Previous Message Pavel Stehule 2026-07-07 20:03:47 Re: POC: PLpgSQL FOREACH IN JSON ARRAY