Re: Planner selects slow "Bitmap Heap Scan" when "Index Scan" is faster - Mailing list pgsql-performance

From Jeff Janes
Subject Re: Planner selects slow "Bitmap Heap Scan" when "Index Scan" is faster
Date
Msg-id CAMkU=1zVGenuzg6UpPW_SHPAJ8CvQ2zS_JRQXYTfQHhxDwE2xQ@mail.gmail.com
Whole thread Raw
In response to Planner selects slow "Bitmap Heap Scan" when "Index Scan" is faster  (Kim Hansen <kim@rthansen.dk>)
Responses Re: Planner selects slow "Bitmap Heap Scan" when "Index Scan" is faster  (Kim Hansen <kim@rthansen.dk>)
List pgsql-performance
On Wed, Apr 4, 2012 at 6:47 AM, Kim Hansen <kim@rthansen.dk> wrote:
> Hi All
>
> I have a query where the planner makes a wrong cost estimate, it looks
> like it underestimates the cost of a "Bitmap Heap Scan" compared to an
> "Index Scan".
>
> This it the two plans, I have also pasted them below:
>  Slow (189ms): http://explain.depesz.com/s/2Wq
>  Fast (21ms): http://explain.depesz.com/s/ThQ

Could you do explain (analyze, buffers)?

Did you run these queries multiple times in both orders?  If you just
ran them once each, in the order indicated, then the bitmap scan may
have done the hard work of reading all the needed buffers into cache,
and the index scan then got to enjoy that cache.

Cheers,

Jeff

pgsql-performance by date:

Previous
From: Julien Cigar
Date:
Subject: Re: bad plan
Next
From: Kim Hansen
Date:
Subject: Re: Planner selects slow "Bitmap Heap Scan" when "Index Scan" is faster