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.96) (envelope-from ) id 1vLXw2-002zRG-1s for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Nov 2025 02:28:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vLXw0-00A0CY-2o for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Nov 2025 02:28:41 +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.96) (envelope-from ) id 1vLXw0-00A0CP-1p for pgsql-hackers@lists.postgresql.org; Wed, 19 Nov 2025 02:28:40 +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 ) id 1vLXvy-000GMF-1v for pgsql-hackers@lists.postgresql.org; Wed, 19 Nov 2025 02:28:40 +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 5AJ2SZA31372794; Tue, 18 Nov 2025 21:28:35 -0500 From: Tom Lane To: Thomas Munro cc: Peter Eisentraut , Kyotaro Horiguchi , pgsql-hackers@lists.postgresql.org Subject: Re: PRI?64 vs Visual Studio (2022) In-reply-to: References: <20250331.152829.1921392690375275165.horikyota.ntt@gmail.com> <001bdc3b-ef94-4f24-b017-ac8ff0a2ea55@eisentraut.org> Comments: In-reply-to Thomas Munro message dated "Wed, 19 Nov 2025 15:13:54 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1372792.1763519315.1@sss.pgh.pa.us> Date: Tue, 18 Nov 2025 21:28:35 -0500 Message-ID: <1372793.1763519315@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > We don't even test -Dnls on the Windows CI task, so the fact that it > passes there doesn't mean much (if our tests would even pick up > expansion failure, not sure). We should probably do > something about that and/or its absence from the build farm. We're > effectively counting on the EDB packaging team or end users to tell us > if we break localisation on this platform. I'm pretty certain that we do not test NLS localization at all, anywhere :-(. (There are no test cases checking enable_nls, which would be a necessary thing to not fail on buildfarm critters not using NLS.) I agree that starting to rely on PRI?64 in translatable strings is raising the bar a good deal, so maybe it's time to do something about that. regards, tom lane