From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: Slow Query- Bad Row Estimate
Date: Fri, 29 Oct 2010 14:09:37 -0700
Message-ID: <4CCB3811.80900@agliodbs.com> (raw)
In-Reply-To: <216FFB77CBFAEE4B8EE4DF0A939FF1D1018354@mail-001.corp.automotive.com>
References: <216FFB77CBFAEE4B8EE4DF0A939FF1D1018354@mail-001.corp.automotive.com>
On 10/29/10 1:54 PM, Ozer, Pam wrote:
> " -> Index Scan using dealergroupgeocache_i01 on
> dealergroupgeocache (cost=0.00..5719.56 rows=9055 width=10) (actual
> time=0.015..87.689 rows=163491 loops=1)"
This appears to be your problem here.
a) when was dealergroupgeocache last ANALYZED?
b) try increasing the stats_target on dealergroupid and regionid, to say
500 and re-analyzing.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: Slow Query- Bad Row Estimate
In-Reply-To: <4CCB3811.80900@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox