Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cZQAk-0004lx-Mk for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Feb 2017 22:48:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cZQAj-0005dr-PD for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Feb 2017 22:48:09 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cZQAj-0005dk-8t for pgsql-bugs@postgresql.org; Thu, 02 Feb 2017 22:48:09 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cZQAh-000587-1X for pgsql-bugs@postgresql.org; Thu, 02 Feb 2017 22:48:08 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v12Mm5gA018420; Thu, 2 Feb 2017 17:48:05 -0500 From: Tom Lane To: crvv.mail@gmail.com cc: pgsql-bugs@postgresql.org Subject: Re: BUG #14524: Commands compare with nested subquery expressions fail with "should not reference subplan var" In-reply-to: <20170202060020.1400.89021@wrigleys.postgresql.org> References: <20170202060020.1400.89021@wrigleys.postgresql.org> Comments: In-reply-to crvv.mail@gmail.com message dated "Thu, 02 Feb 2017 06:00:20 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <18418.1486075685.1@sss.pgh.pa.us> Date: Thu, 02 Feb 2017 17:48:05 -0500 Message-ID: <18419.1486075685@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org crvv.mail@gmail.com writes: > SELECT '1' IN (SELECT (SELECT '1'::BOOL)) > Error message is "plan should not reference subplan's variable". Seems to be a problem with pasting on Material nodes at the last minute. As a short-term workaround, you might try turning off enable_material. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs