| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Blewett <david(at)dawninglight(dot)net> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Bad Plan for Questionnaire-Type Query |
| Date: | 2009-05-07 20:31:43 |
| Message-ID: | 25886.1241728303@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
David Blewett <david(at)dawninglight(dot)net> writes:
> On Thu, May 7, 2009 at 12:53 PM, David Blewett <david(at)dawninglight(dot)net> wrote:
>> 1. http://dpaste.com/hold/41842/
>> 2. http://explain.depesz.com/s/Wg
>> 3. http://explain.depesz.com/s/1s
>> 4. http://dpaste.com/hold/41846/
> Forgot to mention that I'm using Postgres 8.3.6 on linux 2.6.24.
Well, the reason it likes the nestloop plan is the estimate of just one
row out of the lower joins --- that case is pretty much always going to
favor a nestloop over other kinds of joins. If it were estimating even
as few as ten rows out, it'd likely switch to a different plan. So the
question to ask is why the rowcount estimates are so abysmally bad.
You mentioned having tried to increase the stats targets, but without
seeing the actual stats data it's hard to speculate about this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viktor Rosenfeld | 2009-05-07 22:38:58 | Indexes not used in DELETE |
| Previous Message | Simon Riggs | 2009-05-07 19:32:35 | Re: Any better plan for this query?.. |