Re: Unexpected query plan results - Mailing list pgsql-performance

From Robert Haas
Subject Re: Unexpected query plan results
Date
Msg-id 603c8f070905291432o4d0ff1fdo699a21a7092477f5@mail.gmail.com
Whole thread Raw
In response to Unexpected query plan results  (Anne Rosset <arosset@collab.net>)
Responses Re: Unexpected query plan results  (Anne Rosset <arosset@collab.net>)
List pgsql-performance
On Thu, May 28, 2009 at 6:46 PM, Anne Rosset <arosset@collab.net> wrote:
>                                                  ->  Index Scan using
> item_pk on item  (cost=0.00..176865.31 rows=97498 width=88) (actual
> time=117.304..2405.060 rows=71 loops=1)
>                                                        Filter: ((NOT
> is_deleted) AND ((folder_id)::text = 'tracker3641'::text))

The fact that the estimated row count differs from the actual row
count by a factor of more than 1000 is likely the root cause of your
problem here.  You probably want to figure out why that's happening.
How many rows are in that table and what value are you using for
default_statistics_target?

...Robert

pgsql-performance by date:

Previous
From: Anne Rosset
Date:
Subject: Re: Unexpected query plan results
Next
From: Robert Haas
Date:
Subject: Re: Unexpected query plan results