| From: | Laurette Cisneros <laurette(at)nextbus(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | query question |
| Date: | 2002-12-06 23:32:01 |
| Message-ID: | Pine.LNX.4.44.0212061531340.7895-100000@visor.corp.nextbus.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Silly question (and just because I would like to know exactly why):
This query:
select distinct x, y
from table1 t
join table2 t2
using (col1)
order by x;
is *slower* than this query:
select disting x, y
from table1
where col1 = (select col1 from table2)
ORDER BY x;
Is this because in the latter case the select col1 is cached?
Ooo, I would love to have a web page full of these tidbits (along with how
to get around the max and min aggregates and why as an example..., etc.)!
Thanks,
--
Laurette Cisneros
The Database Group
(510) 420-3137
NextBus Information Systems, Inc.
www.nextbus.com
----------------------------------
There is more to life than just SQL.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2002-12-07 00:38:18 | Re: query question |
| Previous Message | Tom Lane | 2002-12-06 23:07:08 | Re: Speeding up aggregates |