Re: Optimizer Path Candidates difference in 9.1.3 and 9.2 beta1

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Optimizer Path Candidates difference in 9.1.3 and 9.2 beta1
Дата
Msg-id 20614.1340770065@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Optimizer Path Candidates difference in 9.1.3 and 9.2 beta1  (Qi Huang <huangqiyx@hotmail.com>)
Ответы Re: Optimizer Path Candidates difference in 9.1.3 and 9.2 beta1  (Qi Huang <huangqiyx@hotmail.com>)
Список pgsql-hackers
Qi Huang <huangqiyx@hotmail.com> writes:
> Hi, hackers    I modified the code in add_path() a bit so that all the query path candidates inside pathlist will not
beremoved and all new path will be added into the pathlist, thus all path candidates are kept in pathlist. I then
testeda four-relation query. In 9.1.3, I can see thousands of candidates in the final RelOptInfo, and some of them are
evenbusy trees. But in 9.2 beta1 which I forked from github, there are no such busy trees and only about 50 join path
intotal, which should match the requirement of System R algo. Is there any modification regarding the system R algo in
thenew release? And something wrong in algo in 9.1.3?    Thanks
 

[ shrug... ]  When you're not showing us exactly what you did, it's hard
to answer that for sure.  But there is some prefiltering logic in
joinpath.c that you might have to lobotomize too if you want to keep
known-inferior join paths.
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Posix Shared Mem patch
Следующее
От: Qi Huang
Дата:
Сообщение: Re: Optimizer Path Candidates difference in 9.1.3 and 9.2 beta1