Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "flavio(dot)ricci82(at)gmail(dot)com" <flavio(dot)ricci82(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16834: where-in: if the nested query fails, the parent query returns all the records
Date: 2021-01-22 15:27:37
Message-ID: CAKFQuwaq1TaGp9E1GKH8KOCe3Ec44XuUesZ87RfkkuV72LfecQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Friday, January 22, 2021, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
>
>
>
> If you run only the nested query it fails because the field does not exist
> for table_b
> If you run all the query, it returns all the records of table_a
>

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

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-01-22 15:56:52 BUG #16835: btree index does not work for where clause using 'foo%'
Previous Message Tom Lane 2021-01-22 15:23:31 Re: BUG #16833: postgresql 13.1 process crash every hour