From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: "lxndrkrlv@gmail.com" <lxndrkrlv@gmail.com>,
        "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17233: Incorrect behavior of DELETE command with bad
 subquery in WHERE clause
In-reply-to: 
 <CAKFQuwbMZNbFpipHhKWDgwy1rjV+T_JhUmGCbKAORu1cuxR8Qw@mail.gmail.com>
References: <17233-afb9d806aaa64b17@postgresql.org>
 <CAKFQuwbnETbhnBYtMA8HNJwf0ipwAETd58=K0JzPs22Of2ZhcA@mail.gmail.com>
 <1409812.1634481258@sss.pgh.pa.us>
 <CAKFQuwbMZNbFpipHhKWDgwy1rjV+T_JhUmGCbKAORu1cuxR8Qw@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Sun, 17 Oct 2021 07:50:24 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1411093.1634482636.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Sun, 17 Oct 2021 10:57:16 -0400
Message-ID: <1411094.1634482636@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1411094.1634482636%40sss.pgh.pa.us>
Precedence: bulk

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> I was actually wondering why the error wasn’t an ambiguous column name
> error.  For a pure select query we already allow duplicate column names in
> the result.

To get an "ambiguous column name" error, there'd need to be multiple
*accessible* names, not multiple inaccessible ones.  Although I concede
your point that maybe we could adjust the "does not exist" phraseology
too.  Maybe something like "column foo is not available"?

			regards, tom lane