Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178])
	by postgresql.org (Postfix) with ESMTP id AF7A74759B5
	for <pgsql-sql@postgresql.org>; Tue, 23 Jul 2002 11:05:54 -0400 (EDT)
Received: by megazone.bigpanda.com (Postfix, from userid 1001)
	id 20554D60A; Tue, 23 Jul 2002 08:05:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by megazone.bigpanda.com (Postfix) with ESMTP
	id 13F435C03; Tue, 23 Jul 2002 08:05:59 -0700 (PDT)
Date: Tue, 23 Jul 2002 08:05:59 -0700 (PDT)
From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Daryl Herzmann <akrherz@iitap.iastate.edu>
Cc: <pgsql-sql@postgresql.org>
Subject: Re: Queries not using Index
In-Reply-To: 
 <Pine.LNX.4.44.0207221505070.6373-100000@pass.physics.iastate.edu>
Message-ID: <20020723080457.V24800-100000@megazone23.bigpanda.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Archive-Number: 200207/351
X-Sequence-Number: 8729


On Mon, 22 Jul 2002, Daryl Herzmann wrote:

> snet=# explain SELECT * from t2002_06 WHERE station = 'SGLI4';
> NOTICE:  QUERY PLAN:
>
> Seq Scan on t2002_06  (cost=0.00..35379.69 rows=35564 width=47)
>
> EXPLAIN

What does explain show if you do set enable_seqscan=off;
?
It's possible that it's estimating a greater cost for the index scan.