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 DE17641B-7F51-49F4-9009-747C8E11DBC6@anarazel.de
Whole thread Raw
In response to Re: Damage control for planner's get_actual_variable_endpoint() runaway  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Damage control for planner's get_actual_variable_endpoint() runaway
Re: Damage control for planner's get_actual_variable_endpoint() runaway
List pgsql-hackers
Hi,

On November 21, 2022 9:37:34 AM PST, Robert Haas <robertmhaas@gmail.com> wrote:
>On Mon, Nov 21, 2022 at 12:30 PM Andres Freund <andres@anarazel.de> wrote:
>> This can't quite be right - isn't this only applying the limit if we found a
>> visible tuple?
>
>It doesn't look that way to me, but perhaps I'm just too dense to see
>the problem?

The earlier version didn't have the issue, but the latest seems to only limit after a visible tuple has been found.
Notethe continue; when fetching a heap tuple fails. 

Andres

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Catalog_xmin is not advanced when a logical slot is lost
Next
From: sirisha chamarthi
Date:
Subject: Re: Catalog_xmin is not advanced when a logical slot is lost