AW: VS2022: Support Visual Studio 2022 on Windows

From: Hans Buschmann <buschmann(at)nidsa(dot)net>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: AW: VS2022: Support Visual Studio 2022 on Windows
Date: 2021-10-13 16:44:53
Message-ID: 1634143495613.6371@nidsa.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

During October Patchday 2021 the Visual Studio components where upraded too.

Now VS2022 Preview 5 is out, also Visual Studio 2022 RC is available to be used for production use (seems like our RC with respect to features).

In the long of this process Microsoft announced the general availability of VS200 for Monday, November 8, see

https://devblogs.microsoft.com/visualstudio/join-us-november-8th-for-the-launch-of-visual-studio-2022/

This date is just some hours after the wrapup for our minor release on November 11.

Barring any objections I suggest to apply the patch just before this weekend in November to have the support for Microsofts Developer Suite for the following 3 months available. (PS: no one is OBLIGUED to use the new version of VS, the interest for PG14 will grow with PG14.1 and this support effects only experienced users self-compiling on windows).

I will watch the development in the first week of November and will update the patch to include the latest version number.

It seems clear that VS2022 will take the 14.30 range as Version number (seen from the VC runtime versions installed)

Only the VisualStudioVersion (17.0.31717.71) will be changed like on EVERY update of a Visual Studio installation/upgrade.

VS2019 is now on 16.11.5, Postgres never upgrades this number for older versions and always uses the initial number when introduced (here 16.0.28729.10 for VS2019).

So it seems safe to use a number of a version which can be used for building PG without errors.

Thanks

Hans Buschmann

________________________________________
Von: Michael Paquier <michael(at)paquier(dot)xyz>
Gesendet: Montag, 11. Oktober 2021 08:03
An: Andrew Dunstan
Cc: Laurenz Albe; Hans Buschmann; pgsql-hackers(at)postgresql(dot)org
Betreff: Re: VS2022: Support Visual Studio 2022 on Windows

On Mon, Oct 04, 2021 at 08:21:52AM -0400, Andrew Dunstan wrote:
> I think we'll want to wait for the official release before we add
> support for it.

Agreed. I am pretty sure that the version strings this patch is using
are going to change until the release happens.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-10-13 16:46:27 Re: pg14 psql broke \d datname.nspname.relname
Previous Message Andres Freund 2021-10-13 16:37:21 Re: [RFC] building postgres with meson