Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oOrPl-0006vr-9A for pgsql-bugs@arkaria.postgresql.org; Fri, 19 Aug 2022 02:07:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oOrPi-0002LW-EU for pgsql-bugs@arkaria.postgresql.org; Fri, 19 Aug 2022 02:07:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oOrPi-0002LN-5s for pgsql-bugs@lists.postgresql.org; Fri, 19 Aug 2022 02:07:10 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oOrPe-00080c-0b for pgsql-bugs@lists.postgresql.org; Fri, 19 Aug 2022 02:07:09 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1oOrPa-005UtD-3e; Thu, 18 Aug 2022 22:07:02 -0400 Date: Thu, 18 Aug 2022 22:07:02 -0400 From: Bruce Momjian To: Tom Lane Cc: "David G. Johnston" , "lxndrkrlv@gmail.com" , "pgsql-bugs@lists.postgresql.org" Subject: Re: BUG #17233: Incorrect behavior of DELETE command with bad subquery in WHERE clause Message-ID: References: <17233-afb9d806aaa64b17@postgresql.org> <1409812.1634481258@sss.pgh.pa.us> <2792105.1660859528@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2792105.1660859528@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Aug 18, 2022 at 05:52:08PM -0400, Tom Lane wrote: > Bruce Momjian writes: > > Feedback? > > > -- test some error cases where LATERAL should have been used but wasn't > > select f1,g from int4_tbl a, (select f1 as g) ss; > > ERROR: column "f1" does not exist > > LINE 1: select f1,g from int4_tbl a, (select f1 as g) ss; > > ^ > > -HINT: There is a column named "f1" in table "a", but it cannot be referenced from this part of the query. > > +HINT: There is a column named "f1" in table "a" and another table so a table-qualified column reference is required. > > That one has gone from accurate to completely wrong. First, it's not > the case that there's more than one possible referent, and second, > table-qualifying the reference wouldn't help. What *would* help here > is adding LATERAL, but I'm not sure if we can easily tell whether that > is the case. My error text was written based on the email report and was just a test to see what queries trigger it. > I think perhaps the existing message is mislabeled: it's not a hint > as written, but errdetail, because it's entirely factual. For this > particular example, what would be on-point is > > DETAIL: There is a column named "f1" in table "a", but it cannot be referenced from this part of the query. > HINT: To reference that column, you must mark this subquery with LATERAL. Yes, the problem is that I don't think we want to just be making a suggestion when we have other cases where LATERAL would not help. > While we don't insist that hints be 100% accurate, it's not good > if they're wildly unhelpful. So I'm not sure if we can determine > whether or not it's likely to be on-point. > > I didn't look too closely at your other examples. Yeah, I think someone will have to have a new idea to improve this. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Indecision is a decision. Inaction is an action. Mark Batterson