Re: Damage control for planner's get_actual_variable_endpoint() runaway - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Damage control for planner's get_actual_variable_endpoint() runaway
Date
Msg-id 210D877F-9C93-4AAA-B333-1A63D96F45E4@anarazel.de
Whole thread Raw
In response to Re: Damage control for planner's get_actual_variable_endpoint() runaway  (Simon Riggs <simon.riggs@enterprisedb.com>)
Responses Re: Re: Damage control for planner's get_actual_variable_endpoint() runaway
List 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 by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Add 64-bit XIDs into PostgreSQL 15
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Prevent instability in contrib/pageinspect's regression test.