Re: Damage control for planner's get_actual_variable_endpoint() runaway

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Damage control for planner's get_actual_variable_endpoint() runaway
Дата
Msg-id 3216176.1669052279@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Damage control for planner's get_actual_variable_endpoint() runaway  (Andres Freund <andres@anarazel.de>)
Ответы Re: Damage control for planner's get_actual_variable_endpoint() runaway  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> This can't quite be right - isn't this only applying the limit if we found a
> visible tuple?

What it's restricting is the number of heap page fetches, which
might be good enough.  We don't have a lot of visibility here
into how many index pages were scanned before returning the next
not-dead index entry, so I'm not sure how hard it'd be to do better.

            regards, tom lane



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Damage control for planner's get_actual_variable_endpoint() runaway
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Damage control for planner's get_actual_variable_endpoint() runaway