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

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Damage control for planner's get_actual_variable_endpoint() runaway
Дата
Msg-id 210D877F-9C93-4AAA-B333-1A63D96F45E4@anarazel.de
обсуждение исходный текст
Ответ на Re: Damage control for planner's get_actual_variable_endpoint() runaway  (Simon Riggs <simon.riggs@enterprisedb.com>)
Ответы Re: Re: Damage control for planner's get_actual_variable_endpoint() runaway  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Дерево обсуждения 
Hi,

On November 21, 2022 10:44:17 AM PST, Simon Riggs <simon.riggs@enterprisedb.com> wrote:
>Robert, something like this perhaps? limit on both the index and the heap.

I don't think we should add additional code / struct members into very common good paths for these limits.

I don't really understand the point of limiting in the index - where would the large number of pages accessed come
from?

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Add 64-bit XIDs into PostgreSQL 15
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pgsql: Prevent instability in contrib/pageinspect's regression test.