Re: Searching for the cause of a bad plan

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Searching for the cause of a bad plan
Дата
Msg-id 13644.1190397220@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Searching for the cause of a bad plan  (Simon Riggs <simon@2ndquadrant.com>)
Ответы Re: Searching for the cause of a bad plan  (Simon Riggs <simon@2ndquadrant.com>)
Список pgsql-performance
Simon Riggs <simon@2ndquadrant.com> writes:
> On Fri, 2007-09-21 at 12:08 -0400, Tom Lane wrote:
>> The reason you get a bad plan is that this rowcount estimate is so far
>> off:

> That's true, but its not relevant,

Yes it is --- the reason it wants to use a hashjoin instead of a
nestloop is exactly that it thinks the loop would iterate too many
times.  (Ten is already too many in this case --- if it had estimated
five rows out of the join, it'd have gone with the nestloop, since
the cost estimate difference at the top level is less than 2x.)

            regards, tom lane

В списке pgsql-performance по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Low CPU Usage
Следующее
От: brauagustin-susc@yahoo.com.ar
Дата:
Сообщение: Re: Low CPU Usage