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 1rpV6F-0072rK-5C for pgsql-bugs@arkaria.postgresql.org; Wed, 27 Mar 2024 15:21:59 +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 1rpV6D-00G72P-VN for pgsql-bugs@arkaria.postgresql.org; Wed, 27 Mar 2024 15:21:57 +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.94.2) (envelope-from ) id 1rpV6D-00G72H-Ly for pgsql-bugs@lists.postgresql.org; Wed, 27 Mar 2024 15:21:57 +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.94.2) (envelope-from ) id 1rpV6A-006it4-2s for pgsql-bugs@lists.postgresql.org; Wed, 27 Mar 2024 15:21:56 +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 42RFLo9J3307820; Wed, 27 Mar 2024 11:21:51 -0400 From: Tom Lane To: Fernando Asulay cc: Laurenz Albe , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #18410: SQL Error [XX000]: ERROR: variable not found in subplan target list In-reply-to: References: <18410-b6ad04652311ce33@postgresql.org> <8773b46bea2f4a57029313c62b02dac80f10f32f.camel@cybertec.at> Comments: In-reply-to Fernando Asulay message dated "Wed, 27 Mar 2024 14:17:11 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3307818.1711552910.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 27 Mar 2024 11:21:50 -0400 Message-ID: <3307819.1711552910@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Fernando Asulay writes: > I really am not sure is a postgres bug, but this error has been reported= before as a postgres bug in the past, It's a symptom of something going wrong during planning. But unless you can reproduce it on stock Postgres, I don't think there is any reason to believe that it's a Postgres bug. In any case, the community has no means to investigate it. You need to file it with the Timescale people; if they conclude there's an underlying Postgres problem, they can come to us with their conclusions. regards, tom lane