From: | Jörg Kiegeland <kiegeland(at)ikv(dot)de> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Cannot interpret EXPLAIN |
Date: | 2009-02-17 14:33:40 |
Message-ID: | 499ACAC4.8010608@ikv.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
I have a query SELECT * FROM myTable WHERE ((myCol = var1) OR (myCol =
var2))
.. which produces the following EXLAIN output:
Index Scan using myIndex on myTable (cost=0.00..8.28 rows=1 width=537)
Filter: ((myCol = $1) OR (myCol = $2))
The index "myIndex" is an index on column "myCol". However I expected an
"Index Cond:" row instead of a "Filter:" row, which normally indicates
performance problems.
Should I rather split the OR and use two SELECT statements to get my
result (var1!=var2)? Namely in this case, "Index Cond:" is outputed by
EXPLAIN.
--Jörg Kiegeland
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-17 15:53:39 | Re: Query composite index range in an efficient way |
Previous Message | Rajesh Kumar Mallah | 2009-02-17 13:25:42 | Re: suggestions for postgresql setup on Dell 2950 , PERC6i controller |