From: | RFLM101(at)aol(dot)com |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Query speed |
Date: | 2003-01-04 09:18:00 |
Message-ID: | e.2ad19487.2b484718@aol.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm working on moving several medium size tables from Oracle to Postgres. The
table I'm dealing with has 210000 rows. I've indexed the table with a simple
single column index on a varchar(30) column that is unique but doesn't have a
unique constraint placed on it.
When I issue a select* from table where column = part,
query speed is great, however, changing the where clause to "where column
like 'part%'" the explain analyze shows the database doing a full table scan
and not utilzing the index which slows the query speed.
Oracles optimizer, on the other hand, will use the index so that there is no
comparison in terms of query speed...
How can I get Postgresql's optimizer to use the index?
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-01-04 10:27:53 | Re: [GENERAL] v7.3.1 Bundled and Released ... |
Previous Message | Bruno Wolff III | 2003-01-04 03:15:08 | Re: ident inconsistency |