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 1vIUNA-0034O9-2T for pgsql-bugs@arkaria.postgresql.org; Mon, 10 Nov 2025 16:04:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vIUM8-001IMm-2j for pgsql-bugs@arkaria.postgresql.org; Mon, 10 Nov 2025 16:03:00 +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 1vIUM8-001IMd-1s for pgsql-bugs@lists.postgresql.org; Mon, 10 Nov 2025 16:03:00 +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 1vIUM4-0070Xw-1a for pgsql-bugs@lists.postgresql.org; Mon, 10 Nov 2025 16:02:58 +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 5AAG2mVN1879802; Mon, 10 Nov 2025 11:02:48 -0500 From: Tom Lane To: Andrey Zhidenkov cc: Heikki Linnakangas , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #19108: Stack overflow duting query parse In-reply-to: References: <19108-13b9dd7a2d30a9cc@postgresql.org> Comments: In-reply-to Andrey Zhidenkov message dated "Mon, 10 Nov 2025 16:23:53 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1879800.1762790568.1@sss.pgh.pa.us> Date: Mon, 10 Nov 2025 11:02:48 -0500 Message-ID: <1879801.1762790568@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrey Zhidenkov writes: >> Can you create a self-contained SQL script to reproduce this, and post it >> on this thread with reply-all, please? > Unfortunately, I cannot reproduce the issue even on an existing 15.7 > node (one that hasn't upgraded) (don't know if it matters, but now it's a > hot standby node) but there are core dumps and debug info packages > installed so I can provide more data from core dump. Could you at least provide a not-mangled-to-the-point-of-incorrectness version of the query? The posted one fails with ERROR: table name "tablename_v2" specified more than once and there are other visible bugs in it. Some clarity about the column data types would be helpful as well. regards, tom lane