Re: Bad planner decision - bitmap scan instead of index

From: Michael Stone <mstone+postgres(at)mathom(dot)us>
To: Frank Schoep <frank(at)ffnn(dot)nl>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Bad planner decision - bitmap scan instead of index
Date: 2007-08-17 15:23:29
Message-ID: 20070817152326.GA3749@mathom.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Aug 17, 2007 at 10:43:18AM +0200, Frank Schoep wrote:
>On Aug 17, 2007, at 9:28 AM, hubert depesz lubaczewski wrote:
>(cost=0.00..37612.76 rows=14221 width=48) (actual time=0.125..13.686
>rows=2000 loops=1)
[snip]
>I'm not an expert at how the planner decides which query plan to use,

Neither am I. :) I do notice that the estimated number of rows is
significantly larger than the real number; you may want to bump up your
statistics a bit to see if it can estimate better.

Mike Stone

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Frank Schoep 2007-08-17 15:59:30 Re: Bad planner decision - bitmap scan instead of index
Previous Message Frank Schoep 2007-08-17 08:43:18 Re: Bad planner decision - bitmap scan instead of index