| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: When to drop src/tools/msvc support |
| Date: | 2023-04-11 17:44:20 |
| Message-ID: | 20230411174420.lq6wp7vzuqmnu3dg@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-Apr-11, Michael Paquier wrote:
> Getting a CI job able to do some validation for MSVC would be indeed
> nice. What's the plan in the buildfarm with this coverage? Would all
> the animals switch to meson (Chocolatey + StrawberryPerl, I assume)
> for the job or will there still be some coverage with MSVC for v16
> there?
If we keep MSVC support in 16, then I agree we should have a CI task for
it -- and IMO we should make ti automatically triggers whenever any
Makefile or meson.build is modified. Hopefully we won't touch them
much now that the branch is feature-frozen, but it could still happen.
Do we have code for it already, even if incomplete?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2023-04-11 17:45:10 | Re: Fix the miss consideration of tuple_fraction during add_paths_to_append_rel |
| Previous Message | Peter Geoghegan | 2023-04-11 17:34:48 | Re: Show various offset arrays for heap WAL records |