On Fri, 2007-09-21 at 17:36 +0200, Denes Daniel wrote:
> Even though I forced the nested loop plan using both indexes (that
> returns the rows in the correct order), there is a needless sort step on
> the top, consuming half of the time even on such small tables.
> Now it's clear why the planner did not choose this plan, why I had to
> force it: because it isn't the best if the sort is still there.
Ordering by parent, child is fairly common but the variation you've got
here isn't that common. You'd need to make a case considering all the
alternatives; nobody will agree without a balanced case that includes
what is best for everyone.
Your EXPLAIN looks edited. Have you also edited the sort costs? They
look slightly higher than we might expect. Please provide the full
normal EXPLAIN output.
In response to
pgsql-performance by date
|Next:||From: Kevin Grittner||Date: 2007-09-21 17:51:57|
|Subject: Re: Low CPU Usage|
|Previous:||From: Simon Riggs||Date: 2007-09-21 17:39:12|
|Subject: Re: Searching for the cause of a bad plan|