From: | Phil Davey <pd213(at)mole(dot)bio(dot)cam(dot)ac(dot)uk> |
---|---|
To: | pgsql-sql <pgsql-sql(at)postgresql(dot)org> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: RES: [SQL] Queries not using Index |
Date: | 2002-07-24 17:12:40 |
Message-ID: | Pine.SGI.4.33.0207241806040.447874-100000@mole.bio.cam.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
On Wed, 24 Jul 2002, Daryl Herzmann wrote:
[lots of chopping and rearranging...]
> snet=# explain analyze select * from t2002_06 WHERE station = 'SAMI4';
> Seq Scan on t2002_06 (cost=0.00..35379.69)
> Total runtime: 2452.14 msec
>
> snet=# set enable_seqscan=off;
> snet=# explain analyze select * from t2002_06 WHERE station = 'SAMI4';
> Index Scan using t2002_06_station_hash_idx on t2002_06
> (cost=0.00..132190.93)
> Total runtime: 325.22 msec
I don't know how these indexes actually work, but just looking at the
numbers here, it uses a seq scan because it thinks a seq scan costs far
less than an index scan (35379 v 132190) even though the actual runtime is
much less for the index scan (2452 msec v 325 msec).
*why* it's guessing wrong, I haven't got a clue. =)
--
Phil Davey
Computer Officer
Hughes Hall College, Cambridge
Email phil(dot)davey(at)hughes(dot)cam(dot)ac(dot)uk
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2002-07-24 17:20:26 | Re: regression test |
Previous Message | Stephan Szabo | 2002-07-24 17:07:45 | Re: Using FTI-Search (likely a more general runtime-puzzle) |
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Lbeck | 2002-07-24 17:24:52 | Function using more than one database |
Previous Message | Elielson Fontanezi | 2002-07-24 16:13:19 | RES: RES: [SQL] Queries not using Index |