Re: Postgres not willing to use an index? - Mailing list pgsql-performance

From Robert Haas
Subject Re: Postgres not willing to use an index?
Date
Msg-id 603c8f070902061012y61da659fp2d93f8ac4eece354@mail.gmail.com
Whole thread Raw
In response to Re: Postgres not willing to use an index?  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Postgres not willing to use an index?  (Mario Splivalo <mario.splivalo@megafon.hr>)
List pgsql-performance
On Fri, Feb 6, 2009 at 12:41 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
>>>> Robert Haas <robertmhaas@gmail.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?

I gather that the results were repeatable, but perhaps Mario could
double-check that?

...Robert

pgsql-performance by date:

Previous
From: Arjen van der Meijden
Date:
Subject: Re: suggestions for postgresql setup on Dell 2950 , PERC6i controller
Next
From: Robert Haas
Date:
Subject: Re: inheritance, and plans