From: Tom Lane <tgl@sss.pgh.pa.us>
To: david@stanaway.net
Cc: pgsql-sql@postgresql.org
Subject: Re: Timestamp index not used
Date: Thu, 08 May 2003 01:26:45 -0400
Message-ID: <17620.1052371605@sss.pgh.pa.us> (raw)
In-Reply-To: <50240.10.0.50.1.1052366175.squirrel@david.stanaway.net>
References: <50240.10.0.50.1.1052366175.squirrel@david.stanaway.net>
<david@stanaway.net> writes:
> radius=# EXPLAIN SELECT * from alldata where loggedat > '2003-05-07';
> NOTICE: QUERY PLAN:
> Seq Scan on alldata (cost=0.00..286136.26 rows=1428487 width=780)
^^^^^^^^^^^^
The planner seems to think that this query will return rather a lot of
rows ... which would imply that a seqscan isn't necessarily a bad idea.
Is that rows estimate accurate? (If not, have you ANALYZEd this table
lately?)
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, david@stanaway.net
Subject: Re: Timestamp index not used
In-Reply-To: <17620.1052371605@sss.pgh.pa.us>
* 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