I am having similar problems at the moment, the query planner seems to be a
little out when deciding which method to use.
I disabled the use of seq scans using
SET ENABLE_SEQSCAN = NO;
and the query that used to take 3.03 minutes now takes 5-7 secs. (v7.0
approx 3.5 million rows)
However this has raised a few questions of my own ie. can this setting be
forced permanently (rather than for each session) and on individual dbs? It
is almost certainly the case that this particular table/db is a special case
and I do not want to force index scans on the other dbs.
Cheers
Graham
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org]On Behalf Of R D
Sent: 12 December 2000 14:20
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Index usage ?
Hi,
I'm making a database with table of over 50 000 000 i
created index on some columns but they are used only
in range search (e.g. WHERE column<100 AND column>10)
and point rearch (e.g. WHERE column=100). When I try
to execute some queries using only <,>,<= or >= index
is not used.
So is there any way to force ysage of the index with
this conditions.
I'm using BTREE as noted in Pg users guide.
please help!
regards,
Rumen
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
