Re: Optimisation of INTERSECT expressions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: Phil Endecott <spam_from_postgresql_lists(at)chezphil(dot)org>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Optimisation of INTERSECT expressions
Date: 2004-03-23 15:47:42
Message-ID: 20715.1080056862@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

Browse pgsql-performance by date

  From Date Subject
Next Message Rosser Schwarz 2004-03-23 16:07:57 Re: atrocious update performance
Previous Message Stephan Szabo 2004-03-23 15:14:46 Re: Optimisation of INTERSECT expressions