From: | Hans-Juergen Schoenig <hs(at)cybertec(dot)at> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | PostgreSQL doesn't use indexes even is enable_seqscan = off |
Date: | 2002-07-07 08:48:51 |
Message-ID: | 3D280073.5010809@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have a severe problem with PostgreSQL 7.2.1.
I have a table containing 500mio records (for testing purposes).
I have indexed the table:
CREATE UNIQUE INDEX idx_one_id ON one(id);
CREATE INDEX idx_one_xmod ON one(xmod);
The index was created properly but somehow it isn't used:
cluster=# \d one
Table "one"
Column | Type | Modifiers
--------+---------+-----------
id | bigint |
even | boolean |
xmod | integer |
Indexes: idx_one_xmod
Unique keys: idx_one_id
cluster=# SET enable_seqscan TO off;
SET VARIABLE
cluster=# SELECT * FROM one WHERE id=300000;
Cancel request sent
ERROR: Query was cancelled.
cluster=# EXPLAIN SELECT * FROM one WHERE id=300000;
NOTICE: QUERY PLAN:
Seq Scan on one (cost=100000000.00..109434714.00 rows=1 width=13)
EXPLAIN
cluster=# SELECT version();
version
-------------------------------------------------------------
PostgreSQL 7.2.1 on i686-pc-linux-gnu, compiled by GCC 2.96
(1 row)
When sequential scans are turned off PostgreSQL should use an index but
it doesn't.
Is it a bug? Have I done something one?
Did anybody face a similar problem?
Hans
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Welche | 2002-07-07 09:12:42 | Re: old 7.2 bug? |
Previous Message | Josh Jore | 2002-07-07 04:38:28 | Re: database backup |