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 1vQavN-00CErC-2S for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Dec 2025 00:40:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vQavM-00AgvW-2D for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Dec 2025 00:40:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vQavM-00AgvO-1L for pgsql-hackers@lists.postgresql.org; Wed, 03 Dec 2025 00:40:52 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vQavK-002pV8-2J for pgsql-hackers@postgresql.org; Wed, 03 Dec 2025 00:40:52 +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 5B30ek0X534127; Tue, 2 Dec 2025 19:40:46 -0500 From: Tom Lane To: Michael Paquier cc: David Geier , 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> Comments: In-reply-to Michael Paquier message dated "Wed, 03 Dec 2025 09:35:52 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <534125.1764722446.1@sss.pgh.pa.us> Date: Tue, 02 Dec 2025 19:40:46 -0500 Message-ID: <534126.1764722446@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > It may be a good idea to split the patch into two parts, at least: > - One for the bulk of the changes, for the straight-forward changes. > Most of what you are suggesting are that for palloc_object and > palloc_array which are dropped-in replacements. Checking that these > assemble the same before and after offers one extra layer of > confidence. > - Second one for the more dubious changes. Yeah, I was thinking the same. Some of those might perhaps be bugs that we want to back-patch, so they need to be looked at in a different way. regards, tom lane