From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | postgresql(at)foo(dot)me(dot)uk, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Slow query: bitmap scan troubles |
Date: | 2012-12-05 17:43:49 |
Message-ID: | CAGTBQpZa4Ru68pu6GiewBZUNk1hw8OObXaks6=Lt+-0qBdhjsg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Wed, Dec 5, 2012 at 2:39 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> I'm not sure that this change would fix your problem, because it might
> also change the costs of the alternative plans in a way that
> neutralizes things. But I suspect it would fix it. Of course, a
> correct estimate of the join size would also fix it--you have kind of
> a perfect storm here.
As far as I can see on the explain, the misestimation is 3x~4x not 200x.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2012-12-05 17:47:57 | Re: Dumping an Extension's Script |
Previous Message | Simon Riggs | 2012-12-05 17:42:23 | Re: ALTER TABLE ... NOREWRITE option |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-12-05 18:05:10 | Re: Slow query: bitmap scan troubles |
Previous Message | Jeff Janes | 2012-12-05 17:39:35 | Re: Slow query: bitmap scan troubles |