On 31-Jul-98 Bruce Momjian wrote:
> I have succeeded in making OR clauses use indexes. I have not dealt
> with some of the more complex issues like x=3 or y=5 as Vadim
> mentioned,
> but at least it works.
>
> test=> select * from test where x=102532 or x=102533;
> x
> ------
> 102532
> 102533
> (2 rows)
>
> test=> explain select * from test where x=102532 or x=102533;
> NOTICE: QUERY PLAN:
>
> Index Scan using i_test on test (cost=4.10 size=1 width=4)
Now I've been wondering why my selects are so slow. Is this telling me
that they're NOT using the index? And if not, any ideas why?
The select returned 35 rows out of approx 170,000.
-----
campsites=> explain select * from locations where lower(city)='oxford';
NOTICE: QUERY PLAN:
Seq Scan on locations (cost=7263.30 size=84899 width=32)
EXPLAIN
campsites=>
-----
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
"There is no outfit less entitled to lecture me about bloat
than the federal government" -- Tony Snow
==========================================================================