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 1vRX5g-00FLbu-0t for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Dec 2025 14:47:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vRX5e-008Q7G-32 for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Dec 2025 14:47:23 +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 1vRX5e-008PzJ-22 for pgsql-hackers@lists.postgresql.org; Fri, 05 Dec 2025 14:47:22 +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 1vRX5c-003I9f-1l for pgsql-hackers@postgresql.org; Fri, 05 Dec 2025 14:47:22 +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 5B5ElHcj1433179; Fri, 5 Dec 2025 09:47:17 -0500 From: Tom Lane To: David Geier cc: Michael Paquier , Thomas Munro , Chao Li , pgsql-hackers Subject: Re: Consistently use palloc_object() and palloc_array() In-reply-to: References: <524587.1764365323@sss.pgh.pa.us> <1e7f0c17-a965-4d5b-ad88-b435a4d97490@gmail.com> <143d3184-b575-49bd-8bc1-f37f45f010cc@gmail.com> <534126.1764722446@sss.pgh.pa.us> <4ab4a12b-49e9-4ebf-9055-225c8055fed0@gmail.com> Comments: In-reply-to David Geier message dated "Fri, 05 Dec 2025 13:53:37 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1433177.1764946037.1@sss.pgh.pa.us> Date: Fri, 05 Dec 2025 09:47:17 -0500 Message-ID: <1433178.1764946037@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Geier writes: > My bad. I hadn't realized that - obviously - not necessarily all code is > actually compiled by default. > Will the build system enable any target for which all dependencies (e.g. > libraries) are met, or are there targets that need to be enabled > explicitly? Is there a way to enable all of them so I can easily make > sure, I actually compile all code? There's a good deal of platform-specific code in PG, particularly for Windows, and obviously none of that will be built unless you're on the right platform. (You can reach some of the Windows-specific code on other systems with -DEXEC_BACKEND, but that goes only so far.) As for optional-feature stuff, I think the meson build system will by default build every option it can find the supporting libraries for. But the other side of that coin is that if you didn't install the right packages it will silently not build it. I think the most reliable way is to look at "./configure --help" and select all the options you think should work on your platform. Then, if you forgot to install libfoo-devel or whatever, you'll get configure failures. regards, tom lane