Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1uYmbX-00BK1V-3E
	for pgsql-hackers@arkaria.postgresql.org; Mon, 07 Jul 2025 14:13:59 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1uYmbS-002dtj-OT
	for pgsql-hackers@arkaria.postgresql.org; Mon, 07 Jul 2025 14:13:55 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uYmbS-002dtM-C3
	for pgsql-hackers@lists.postgresql.org; Mon, 07 Jul 2025 14:13:55 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1uYmbR-0063BH-0M
	for pgsql-hackers@postgresql.org;
	Mon, 07 Jul 2025 14:13:53 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 567EDlt2387477;
	Mon, 7 Jul 2025 10:13:47 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nazir Bilal Yavuz <byavuz81@gmail.com>
cc: Peter Eisentraut <peter@eisentraut.org>,
        Andrew Dunstan <andrew@dunslane.net>,
        Michael Paquier <michael@paquier.xyz>,
        pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: C11 / VS 2019
In-reply-to: 
 <CAN55FZ03ZXUFsxiyR0hzFsrYG-jbQzt8=uoC8b16THu3kU92fg@mail.gmail.com>
References: <01a69441-af54-4822-891b-ca28e05b215a@eisentraut.org>
 <aD2sgK4tMVumNxt4@nathan> <aD5_OiEKEz2RpYFR@paquier.xyz>
 <b4af1f32-f90f-4670-9598-029e99b69f31@eisentraut.org>
 <e5488fe3-38d5-4b1f-ae0d-a254dc969f16@eisentraut.org>
 <90506.1751754464@sss.pgh.pa.us>
 <46154df9-f514-4d79-89bb-df4af46b1b9f@eisentraut.org>
 <CAN55FZ03ZXUFsxiyR0hzFsrYG-jbQzt8=uoC8b16THu3kU92fg@mail.gmail.com>
Comments: In-reply-to Nazir Bilal Yavuz <byavuz81@gmail.com>
	message dated "Mon, 07 Jul 2025 16:19:39 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <387475.1751897627.1@sss.pgh.pa.us>
Date: Mon, 07 Jul 2025 10:13:47 -0400
Message-ID: <387476.1751897627@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/387476.1751897627%40sss.pgh.pa.us>
Precedence: bulk

Nazir Bilal Yavuz <byavuz81@gmail.com> writes:
> On Mon, 7 Jul 2025 at 13:51, Peter Eisentraut <peter@eisentraut.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