| From: | Hans Buschmann <buschmann(at)nidsa(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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-11-06 09:29:34 |
| Message-ID: | 1636190990102.79226@nidsa.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Now it is three days before release of VS2022.
I updated to the latest Preview 7 (= RC3) and recompiled PG14 64bit Release without issues.
There seem to be not many internal differences from previous versions in the tools used for building Postgres.
My intention for an early support is to catch the momentum for signalling to any user: "We support current tools".
The risks seem non-existent.
Updated the patch to reflect the VisualStudioVersion for Preview 7, which is the version number compiled into the main devenv.exe image.
This version number seems to be of no interest elsewhere in the postgres source tree.
I will reflect any updates after official release on monday, November 8
Hans Buschmann
| Attachment | Content-Type | Size |
|---|---|---|
| 0001_support_vs2022_v2.patch | application/octet-stream | 7.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2021-11-06 10:03:23 | Re: using extended statistics to improve join estimates |
| Previous Message | Mark Dilger | 2021-11-06 08:04:48 | Re: Extending amcheck to check toast size and compression |