Re: Optimization outcome depends on the index order

Поиск
Список
Период
Сортировка
От Alexander Korotkov
Тема Re: Optimization outcome depends on the index order
Дата
Msg-id CAPpHfduuwDhxZa496O5cpF3hLbv+m-XV6Qn8=xTpDwXGQ1=3Pg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Optimization outcome depends on the index order  (Andrei Lepikhov <a.lepikhov@postgrespro.ru>)
Ответы Re: Optimization outcome depends on the index order  (Andrei Lepikhov <a.lepikhov@postgrespro.ru>)
Список pgsql-hackers
On Fri, Dec 22, 2023 at 7:24 PM Andrei Lepikhov
<a.lepikhov@postgrespro.ru> wrote:
> On 22/12/2023 11:48, Alexander Korotkov wrote:
> >  > Because we must trust all predictions made by the planner, we just
> >  > choose the most trustworthy path. According to the planner logic, it is
> >  > a path with a smaller selectivity. We can make mistakes anyway just
> >  > because of the nature of estimation.
> >
> > Even if we need to take selectivity into account here, it's still not
> > clear why this should be on top of other logic later in add_path().
> I got your point now, thanks for pointing it out. In the next version of
> the patch selectivity is used as a criteria only in the case of COSTS_EQUAL.

It looks better now.  But it's hard for me to judge these heuristics
in add_path().  Tom, what do you think about this?

------
Regards,
Alexander Korotkov



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

Предыдущее
От: Richard Guo
Дата:
Сообщение: Re: Avoid computing ORDER BY junk columns unnecessarily
Следующее
От: Ayush Vatsa
Дата:
Сообщение: Re: Proposal to include --exclude-extension Flag in pg_dump