opt: fix infinite cost estimate for lookup join with limit hint #46440
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to a divide-by-zero error, the coster estimated an infinite limit hint --
and therefore an infinite cost -- for lookup joins that had a limit hint and
zero output rows. This caused an internal error during planning.
This commit fixes the problem by fixing the divide-by-zero error. Instead of
an infinite limit hint, it estimates a limit hint of 0.
Fixes #46187
Release justification: This is a low risk, high benefit change to existing
functionality.
Release note (bug fix): Fixed an internal error that could occur during
planning for some queries with a join and negative LIMIT.