From: | "Ilker Egilmez" <ilker(at)gate5(dot)de> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | problem: index on number not honoured |
Date: | 2001-11-12 20:06:16 |
Message-ID: | 9spaa8$inv$1@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
hi,
an index on a table column of any number type only gets honoured if you
query it like a string, e.g.
create table t1 ( n int2 ) ;
create index t1n on t1 (n) ;
explain select * from t1 where n = 1 ;
-- Seq Scan on t1 (cost=0.00..22.50 rows=10 width=2)
explain select * from t1 where n = '1' ;
-- Index Scan using t1n on t1 (cost=0.00..8.14 rows=10 width=2)
first i thought this might be an psql client error and tried the same via
jdbc, and look, there it happens again. if i create a PreparedStatemnt and
bind the INT or LONG value with setLong (1,x) the index won't be used in the
select statement. if i bind the value with a setString (1,x+"") command,
then the index is honored correctly. I tested the code against postgres
7.1.3 as well as 7.0.2. this means that i would have to change all my java
code from setLong to setString in order to speed up my apps every time i
query a number. quite ugly!
ilker -)
--
--
gate5 AG
schoenhauser allee 62
10437 berlin
fon + 49 30 446 76 0
fax + 49 30 446 76 555
http://www.gate5.de/ | ilker(at)gate5(dot)de
--
--
gate5 AG
schoenhauser allee 62
10437 berlin
fon + 49 30 446 76 0
fax + 49 30 446 76 555
http://www.gate5.de/ | ilker(at)gate5(dot)de
From | Date | Subject | |
---|---|---|---|
Next Message | charles | 2001-11-12 22:51:24 | pg locking problem |
Previous Message | Brent Verner | 2001-11-12 19:32:19 | Re: rename index? |
From | Date | Subject | |
---|---|---|---|
Next Message | Orion | 2001-11-12 20:37:40 | Re: Funny Parse Error on Insert |
Previous Message | Orion | 2001-11-12 19:12:18 | Funny Parse Error on Insert |