| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: C11 / VS 2019 |
| Date: | 2025-07-07 14:13:47 |
| Message-ID: | 387476.1751897627@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> writes:
> On Mon, 7 Jul 2025 at 13:51, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>> Hmm. We have the (allegedly) same VS version in Cirrus CI, and it's
>> never shown a problem like this.
> CI uses the latest VS 2019 (v16.11.48), it looks like buildfarm member
> drongo uses VS 2019 v16.3.1. I created a custom Windows VM with the
> same VS 2019 version (v16.3.1) at the drongo and CI failed with the
> same error [1].
Huh. Can we trawl the release notes for VS and see if this was
acknowledged as a bug fix, and if so when did it happen? I think
whether we can say "get a newer compiler" depends in part on how
long it's been fixed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikita Malakhov | 2025-07-07 14:33:11 | Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem) |
| Previous Message | Maksim.Melnikov | 2025-07-07 14:05:59 | Panic during xlog building with big values |