Re: Planner selects slow "Bitmap Heap Scan" when "Index Scan" is faster

["Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>]

Kim Hansen <kim@xxxxxxxxxxx> wrote:
 
> 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".
 
> What can I do to fix the cost estimate?
 
Could you try running the query with cpu_tuple_cost = 0.05 and let
us know how that goes?
 
-Kevin

-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance