From: | "Alaric B(dot) Snell" <abs(at)frontwire(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Query planner isn't using my indices |
Date: | 2002-01-08 21:42:13 |
Message-ID: | Pine.LNX.4.43.0201082106100.311-100000@calvin.frontwire.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
To cut a long story short, my largish development database was running the
query I was tinkering with very slowly.
Looking a little deeper, I found that it was always doing a full table
scan.
Which is odd, seeing as we're selecting on a uniquely indexed field...
frontwire=# \d stakeholder_pk
Index "stakeholder_pk"
Attribute | Type
-----------+--------
id | bigint
unique btree
frontwire=# explain select * from stakeholder where id = 1;
NOTICE: QUERY PLAN:
Seq Scan on stakeholder (cost=0.00..602.81 rows=1 width=336)
EXPLAIN
frontwire=# select count(*) from stakeholder;
count
-------
9170
(1 row)
...why is this happening? It... shouldn't!
ABS
--
Alaric B. Snell, Developer
abs(at)frontwire(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2002-01-08 21:53:34 | Re: sequential scans and the like operator |
Previous Message | Doug McNaught | 2002-01-08 21:39:23 | Re: plpgsql |