From: James Russell <internationalhobo@gmail.com>
To: Michael Fuhr <mike@fuhr.org>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Sequential scan being used despite indexes
Date: Wed, 1 Feb 2006 13:33:08 +0900
Message-ID: <3a3a16930601312033w2e4e3186k8f502e5b8c2cc6f2@mail.gmail.com> (raw)
In-Reply-To: <20060201035803.GA6324@winnie.fuhr.org>
References: <3a3a16930601311914w5bd7d1d0hde7b4e495e0deb27@mail.gmail.com>
<43E02B2F.9070202@commandprompt.com>
<20060201035803.GA6324@winnie.fuhr.org>
[Sorry, my last reply didn't go to the list]
Reading about this issue further in the FAQ, it seems that I should ensure
that Postgres has adequate and accurate information about the tables in
question by regularly running VACUUM ANALYZE, something I don't do
currently.
I disabled SeqScan as per the FAQ, and it indeed was a lot slower so
Postgres was making the right choice in this case.
Many thanks,
James
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: internationalhobo@gmail.com, mike@fuhr.org, jd@commandprompt.com
Subject: Re: Sequential scan being used despite indexes
In-Reply-To: <3a3a16930601312033w2e4e3186k8f502e5b8c2cc6f2@mail.gmail.com>
* 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