Re: BUG #13391: when use in/= & subquery, non exists column can elected.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "digoal(at)126(dot)com" <digoal(at)126(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13391: when use in/= & subquery, non exists column can elected.
Date: 2015-06-02 16:14:09
Message-ID: CAKFQuwbHQEfUBFGGFW=pD4zbZjmXsh6JW7qwunpt7MjwVUgWwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tuesday, June 2, 2015, <digoal(at)126(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 13391
> Logged by: digoal
> Email address: digoal(at)126(dot)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.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Gavin Flower 2015-06-02 19:19:23 Re: postgres documentation - proposed improvement/clarification
Previous Message Fujii Masao 2015-06-02 16:04:40 Re: BUG #13368: standby cluster immediately promotes after pg_basebackup from previously promoted master