Horton

Re: BUG #17233: Incorrect behavior of DELETE command with bad subquery in WHERE clause

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Bruce Momjian <bruce@momjian.us>, "David G. Johnston" <david.g.johnston@gmail.com>, "lxndrkrlv@gmail.com" <lxndrkrlv@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2022-11-22T23:49:50Z
Lists: pgsql-bugs 
I wrote:
> So here's a revision that tries to clean that up a little.  0001 is the
> same patch as before, and then 0002 revises the fuzzy-search logic enough
> that I can make sense of it.  I split them mainly so that you can see the
> behavioral difference in the changed test outputs.

Hearing no further comments, pushed.

			regards, tom lane

Commits

  1. Give better hints for ambiguous or unreferenceable columns.

  2. Make subquery aliases optional in the FROM clause.