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

From Tom Lane
Subject Re: Damage control for planner's get_actual_variable_endpoint() runaway
Date
Msg-id 3216176.1669052279@sss.pgh.pa.us
Whole thread Raw
In response to Re: Damage control for planner's get_actual_variable_endpoint() runaway  (Andres Freund <andres@anarazel.de>)
Responses Re: Damage control for planner's get_actual_variable_endpoint() runaway
List 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 by date:

Previous
From: Robert Haas
Date:
Subject: Re: Damage control for planner's get_actual_variable_endpoint() runaway
Next
From: Robert Haas
Date:
Subject: Re: Damage control for planner's get_actual_variable_endpoint() runaway