Re: searching using indexes 8.3 - Mailing list pgsql-general

From Alban Hertroys
Subject Re: searching using indexes 8.3
Date
Msg-id 43D2ACBC-6215-43B4-8831-9C3FBA17C6C4@solfertje.student.utwente.nl
Whole thread Raw
In response to searching using indexes 8.3  (LARC/J.L.Shipman/jshipman <jeffery.l.shipman@nasa.gov>)
List pgsql-general
On Mar 10, 2008, at 6:33 PM, LARC/J.L.Shipman/jshipman wrote:

> Hi,
>     When I do a search such as:
>
>  EXPLAIN ANALYZE SELECT * FROM itemsbyauthor;
>                                                     QUERY PLAN
> ----------------------------------------------------------------------
> ---------------------------------------------
>  Seq Scan on itemsbyauthor  (cost=0.00..971.34 rows=53634 width=34)
> (actual time=0.029..25.831 rows=53634 loops=1)
>  Total runtime: 34.851 ms
> (2 rows)
>
>
> I have an index for the table, but it is not being utilized.  Why
> is this?  How do I get the index to be used?


To fetch all rows unordered from a table the fastest method is a
sequential scan. An index scan would be slower, probably significantly.

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.


!DSPAM:737,47d5748b233097069826464!



pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: ISO something like "#if 0 ... #endif" for SQL code
Next
From: Dimitri Fontaine
Date:
Subject: Re: [PERFORM] multi-threaded pgloader makes it in version 2.3.0