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 1vazQy-00H4hr-0f for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Dec 2025 16:52:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vazQx-006xKm-0J for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Dec 2025 16:52:27 +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 1vazQw-006xKe-2i for pgsql-bugs@lists.postgresql.org; Wed, 31 Dec 2025 16:52:27 +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 1vazQw-003Wfu-0e for pgsql-bugs@lists.postgresql.org; Wed, 31 Dec 2025 16:52:26 +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 5BVGqL4v3922311; Wed, 31 Dec 2025 11:52:21 -0500 From: Tom Lane To: Masahiko Sawada cc: evsi@amazon.com, pgsql-bugs@lists.postgresql.org, Andres Freund Subject: Re: BUG #19368: f54af9f does not create the correct macro for autotools build In-reply-to: References: <19368-016d79a7f3a1c599@postgresql.org> <3917069.1767196772@sss.pgh.pa.us> Comments: In-reply-to Masahiko Sawada message dated "Wed, 31 Dec 2025 08:50:00 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3922309.1767199941.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 31 Dec 2025 11:52:21 -0500 Message-ID: <3922310.1767199941@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Masahiko Sawada writes: > On Wed, Dec 31, 2025 at 7:59 AM Tom Lane wrote: >> This is indeed busted, but I'd argue that the autoconf build has the >> right macro name and meson and the C code are using the wrong one: > Agreed. The attached patch should fix the issue. You beat me to it ;-). Patch LGTM. regards, tom lane