Re: Ideas of "printing out" the alternative paths

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Ideas of "printing out" the alternative paths
Дата
Msg-id 15988.1384448512@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Ideas of "printing out" the alternative paths  (Zhan Li <zhanli89@gmail.com>)
Ответы Re: Ideas of "printing out" the alternative paths  (Zhan Li <zhanli89@gmail.com>)
Список pgsql-hackers
Zhan Li <zhanli89@gmail.com> writes:
> When searching all the possible paths of executing a query, the optimizer
> finds and saves the cheapest paths for the top level rel. I'd like to check
> out all the paths the optimizer has ever considered, which I believe, are
> stored in the pathlist of the top level rel.

No, most of them have been thrown away long before that.  See add_path.
Also realize that in a large join problem, a lot of potential plans never
get explicitly considered, because the input paths get pruned before we
get to considering the join rel at all.  (If this were not so, planning
would take too long.)

People have experimented with having add_path print something about each
path that's fed to it, but the output tends to be voluminous and not all
that useful.
        regards, tom lane



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

Предыдущее
От: Hannu Krosing
Дата:
Сообщение: Re: additional json functionality
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Optimize kernel readahead using buffer access strategy