Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> Given a non-unique A, C1 as B>5, c2 as C>5 and the data:
> A | B | C
> 1 | 6 | 1
> 1 | 1 | 6
> The intersect gives 1 row, the and query gives 0 AFAICS.
Another way that the queries are not equivalent is that INTERSECT is
defined to remove duplicate output rows (much like DISTINCT) whereas
the AND form of course won't do that.
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Rosser Schwarz||Date: 2004-03-23 16:07:57|
|Subject: Re: atrocious update performance|
|Previous:||From: Stephan Szabo||Date: 2004-03-23 15:14:46|
|Subject: Re: Optimisation of INTERSECT expressions|