Re: Postgres not willing to use an index?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Mario Splivalo" <mario(dot)splivalo(at)megafon(dot)hr>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Postgres not willing to use an index?
Date: 2009-02-06 17:41:12
Message-ID: 498C21D8.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>>> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> What's weird about this example is that when he sets enable_seqscan
to
> off, the bitmap index scan plan is actually substantially faster,
even
> though it in fact does scan nearly the entire heap. I don't
> understand how it can be faster to scan the index and the heap than
to
> just scan the heap.

It's cached in the second test, maybe?

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Arjen van der Meijden 2009-02-06 17:53:22 Re: suggestions for postgresql setup on Dell 2950 , PERC6i controller
Previous Message Scott Marlowe 2009-02-06 17:36:47 Re: suggestions for postgresql setup on Dell 2950 , PERC6i controller