| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: When to drop src/tools/msvc support |
| Date: | 2023-04-11 16:23:05 |
| Message-ID: | 20230411162305.cksp3a6ouha3vmwb@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2023-04-11 09:05:31 +0100, Dave Page wrote:
> Probably my main concern is that the Meson build can use the same version
> of the VC++ compiler that we use (v14), which is carefully matched for
> compatibility with all the various components, just in case anything passes
> CRT pointers around.
FWIW, Independent of meson, I don't think support for VC 2015 in postgres is
long for the world. Later versions of msvc have increased the C standard
compliance a fair bit... It's also a few years out of normal support.
I've not tested building with 2015, but I don't know of anything that should
prevent building with meson with it. I am fairly sure that it can't build
tab-complete.c, but you're presumably not building with tab completion support
anyway?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2023-04-11 16:33:01 | Re: Should we remove vacuum_defer_cleanup_age? |
| Previous Message | Ankit Kumar Pandey | 2023-04-11 15:49:12 | [BUG #17888] Incorrect memory access in gist__int_ops for an input array with many elements |