| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Hans Buschmann <buschmann(at)nidsa(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: VS2022: Support Visual Studio 2022 on Windows |
| Date: | 2021-11-24 11:36:27 |
| Message-ID: | YZ4juwMA9wLtpBQV@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 24, 2021 at 10:00:19AM +0000, Dave Page wrote:
> It's extremely unlikely that we'd shift to such a new version for PG15. We
> build many components aside from PostgreSQL, and need to use the same
> toolchain for all of them (we've had very painful experiences with mix n
> match CRT versions in the past) so it's not just PG that needs to support
> VS2022 as far as we're concerned
Yes, I can understand that upgrading the base version of VS used is a
very difficult exercise. I have been through that, on Windows for
Postgres.. As well as for the compilation of all its dependencies.
> - Perl, Python, TCL, MIT Kerberos,
> OpenSSL, libxml2, libxslt etc. are all built with the same toolchain for
> consistency.
Dave, do you include LZ4 in 14? Just asking, as a matter of
curiosity.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2021-11-24 11:43:35 | Re: Skipping logical replication transactions on subscriber side |
| Previous Message | Michael Paquier | 2021-11-24 11:28:33 | Re: [BUG]Missing REPLICA IDENTITY check when DROP NOT NULL |