Skip site navigation (1) Skip section navigation (2)

Re: Unexpected query plan results

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Anne Rosset <arosset(at)collab(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Unexpected query plan results
Date: 2009-05-29 21:32:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Thu, May 28, 2009 at 6:46 PM, Anne Rosset <arosset(at)collab(dot)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


In response to


pgsql-performance by date

Next:From: Robert HaasDate: 2009-05-29 21:34:02
Subject: Re: Unexpected query plan results
Previous:From: Anne RossetDate: 2009-05-29 21:31:57
Subject: Re: Unexpected query plan results

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group