From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-performance@postgresql.org
Cc: robin.c.smith@bt.com
Subject: Re: Forcing using index instead of sequential scan?
Date: Fri, 21 Jul 2006 13:45:41 +0200
Message-ID: <200607211345.41573.peter_e@gmx.net> (raw)
In-Reply-To: <D012B9600FFB984AB18C0D53C475A4A081F51B@E03MVZ3-UKDY.domain1.systemhost.net>
References: <D012B9600FFB984AB18C0D53C475A4A081F51B@E03MVZ3-UKDY.domain1.systemhost.net>
robin.c.smith@bt.com wrote:
> What is the best way to force the use of indexes in these queries?
Well, the brute-force method is to use SET enable_seqscan TO off, but if
you want to get to the bottom of this, you should look at or post the
EXPLAIN ANALYZE output of the offending queries.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: peter_e@gmx.net, robin.c.smith@bt.com
Subject: Re: Forcing using index instead of sequential scan?
In-Reply-To: <200607211345.41573.peter_e@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox