Re: BUG #13391: when use in/= & subquery, non exists column can elected. - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #13391: when use in/= & subquery, non exists column can elected.
Date
Msg-id CAKFQuwbHQEfUBFGGFW=pD4zbZjmXsh6JW7qwunpt7MjwVUgWwQ@mail.gmail.com
Whole thread Raw
In response to BUG #13391: when use in/= & subquery, non exists column can elected.  (digoal@126.com)
List pgsql-bugs
On Tuesday, June 2, 2015, <digoal@126.com> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      13391
> Logged by:          digoal
> Email address:      digoal@126.com <javascript:;>
> PostgreSQL version: 9.4.2
> Operating system:   CentOS 6.x x64
> Description:
>
> when use in/= & subquery, non exists column can elected.
> for exp:
>
> postgres=# explain (analyze,verbose) select * from table1 where c1 =
> (select
> c1 from table2 limit 1);
>
>
This is a correlated subquery, not a bug.

David J.

pgsql-bugs by date:

Previous
From: Fujii Masao
Date:
Subject: Re: BUG #13368: standby cluster immediately promotes after pg_basebackup from previously promoted master
Next
From: Gavin Flower
Date:
Subject: Re: postgres documentation - proposed improvement/clarification