From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | "Staff, Alexander" <alexander(dot)staff(at)sap(dot)com> |
Cc: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Index Usage Question |
Date: | 2003-10-27 14:40:39 |
Message-ID: | Pine.LNX.4.33.0310270740220.14359-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 24 Oct 2003, Staff, Alexander wrote:
> Hi,
> I created a simple table (name char200, zip char10, city char200, street char200, id int) and filled some data, appr. 250 000 records, in it.
> I tested accessing some rows (select id from address where id = 44444;, select * from address where id between 33333, 333444) with an unique index on id and without an index. EXPLAIN tells me in both cases that it does NOT use the index.
> I tested this with using the name column (select name from address where name like 'Wal%';, select name from address where name = 'Walz') and if I created an index on name it uses it.
> Using id in the where clause of the select is as slow as using an unindexed name in the where-clause.
> I ran ANALYZE, no changes.
> What's this ?
> This is not a feature, is it ?
Can we see the output of explain analyze select...(your query here)???
From | Date | Subject | |
---|---|---|---|
Next Message | Sergei Levchenko | 2003-10-27 14:42:10 | connectby |
Previous Message | Andrew Sullivan | 2003-10-27 14:28:41 | Re: Casing: bug? |