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 ) id 1tO4JU-003t6Z-Cl for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Dec 2024 00:22:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tO4JT-004K1G-0N for pgsql-hackers@arkaria.postgresql.org; Thu, 19 Dec 2024 00:22:46 +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.94.2) (envelope-from ) id 1tO4JS-004K18-NI for pgsql-hackers@lists.postgresql.org; Thu, 19 Dec 2024 00:22:46 +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.94.2) (envelope-from ) id 1tO4JP-000Uq2-CW for pgsql-hackers@postgresql.org; Thu, 19 Dec 2024 00:22:45 +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 4BJ0Merh2838706; Wed, 18 Dec 2024 19:22:40 -0500 From: Tom Lane To: Richard Guo cc: David Rowley , Nathan Bossart , Paul Ramsey , PostgreSQL Hackers Subject: Re: Pg18 Recursive Crash In-reply-to: References: <99F064C1-B3EB-4BE7-97D2-D2A0AA487A71@cleverelephant.ca> <2493001.1734473089@sss.pgh.pa.us> Comments: In-reply-to Richard Guo message dated "Thu, 19 Dec 2024 09:11:39 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2838704.1734567760.1@sss.pgh.pa.us> Date: Wed, 18 Dec 2024 19:22:40 -0500 Message-ID: <2838705.1734567760@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Richard Guo writes: > I see. I didn't notice any real issues with that; I was just flagged > by the XXX comment there, which raises the question of whether it's > worth working harder to determine the inputOps. I was intending to add some code to my nodeSetop patch to see if both input plan nodes use the same fixed slot type, and if so pass that rather than NULL to BuildTupleHashTableExt. Perhaps nodeRecursiveunion could do the same thing (in which case we probably ought to abstract that out to a subroutine). regards, tom lane