X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id A634C9DCBFE
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed,  1 Feb 2006 00:33:12 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 41079-09
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed,  1 Feb 2006 00:33:11 -0400 (AST)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.206])
	by postgresql.org (Postfix) with ESMTP id 642239DCBFF
	for <pgsql-performance@postgresql.org>;
	Wed,  1 Feb 2006 00:33:09 -0400 (AST)
Received: by uproxy.gmail.com with SMTP id h2so138260ugf
	for <pgsql-performance@postgresql.org>;
	Tue, 31 Jan 2006 20:33:09 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=FcCi4c1RUxyVmaSBruxgElDlnmD25ecA4kdk91zBBkVaay/ixebOTwKJchdIflzZUMs5IEfmGTZjrUQjWlEjRKhejnT4aZ7GUqWpgR5YBdNhnEP/ZE4egNpgXsGb7hwWhtA40BomCSQq/yFql2Jp9wq4PqtsBexZfvUM7vACHDg=
Received: by 10.49.85.9 with SMTP id n9mr1547810nfl;
	Tue, 31 Jan 2006 20:33:08 -0800 (PST)
Received: by 10.49.59.5 with HTTP; Tue, 31 Jan 2006 20:33:08 -0800 (PST)
Message-ID: <3a3a16930601312033w2e4e3186k8f502e5b8c2cc6f2@mail.gmail.com>
Date: Wed, 1 Feb 2006 13:33:08 +0900
From: James Russell <internationalhobo@gmail.com>
To: Michael Fuhr <mike@fuhr.org>
Subject: Re: Sequential scan being used despite indexes
Cc: "Joshua D. Drake" <jd@commandprompt.com>, pgsql-performance@postgresql.org
In-Reply-To: <20060201035803.GA6324@winnie.fuhr.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_725_20274905.1138768388962"
References: <3a3a16930601311914w5bd7d1d0hde7b4e495e0deb27@mail.gmail.com>
	<43E02B2F.9070202@commandprompt.com>
	<20060201035803.GA6324@winnie.fuhr.org>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=1.774 required=5 tests=[AWL=-0.201, HTML_00_10=0.642,
	HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.332]
X-Spam-Score: 1.774
X-Spam-Level: *
X-Archive-Number: 200602/2
X-Sequence-Number: 16988

------=_Part_725_20274905.1138768388962
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

[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

------=_Part_725_20274905.1138768388962
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

[Sorry, my last reply didn't go to the list]<br>
<br>
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 d=
o currently.<br>

<br>

I disabled SeqScan as per the FAQ, and it indeed was a lot slower so Postgr=
es was making the right choice in this case.<br><br>
Many thanks,<br>
<br>
James<br>

------=_Part_725_20274905.1138768388962--