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 3460861.1669134900@sss.pgh.pa.us
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: Damage control for planner's get_actual_variable_endpoint() runaway
List pgsql-hackers
Simon Riggs <simon.riggs@enterprisedb.com> writes:
> New patch version reporting for duty, sir. Please take it from here!

Why the CHECK_FOR_INTERRUPTS?  I'd supposed that there's going to be
one somewhere down inside the index or heap access --- do you have
reason to think there isn't?

Is it appropriate to count distinct pages, rather than just the
number of times we have to visit a heap tuple?  That seems to
complicate the logic a good deal, and I'm not sure it's buying
much, especially since (as you noted) it's imprecise anyway.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: fixing CREATEROLE
Next
From: Simon Riggs
Date:
Subject: Re: Slow standby snapshot