Re: Possible wrong result with some "in" subquery with non-existing columns

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Xiong He <iihero(at)qq(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Possible wrong result with some "in" subquery with non-existing columns
Date: 2023-01-17 15:07:31
Message-ID: CAKFQuwZNmYHx_ebnw1utp7BkSH2ogqcdgjAxfHtGkpOh2s=mUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tuesday, January 17, 2023, Xiong He <iihero(at)qq(dot)com> wrote:

> Thanks. Tom.
> I think it just makes sense. It doesn't matter if the user knows how to
> express the real query.
> Possibly it's better to emphasize this scenario as an example in the
> official document :-)
>

It is in the FAQ:

https://wiki.postgresql.org/wiki/FAQ#Why_doesn.27t_PostgreSQL_report_a_column_not_found_error_when_using_the_wrong_name_in_a_subquery.3F

Where specifically in the docs would you put this, and how would be it be
presented?

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2023-01-17 20:04:32 Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
Previous Message Amit Kapila 2023-01-17 10:56:22 Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1