planner, stats: overflow estimation may lead to wrong join reorder (#56752)

[ti-chi-bot]

This is an automated cherry-pick of #56752

What problem does this PR solve?

Issue Number: close #56704

Problem Summary:

What changed and how does it work?

When the width of the histogram is tooooo large, it's possible that right bound - left bound exceeds MaxFloat64. Then the width becomes inf, and the later calculation is likely to create NaN.

Join reorder uses MaxFloat64 to do the cost comparison, which leads to the wrong order in the above extreme case.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Fix the case that the cost estimation may get INF/NaN in some extreme situations. And fix the wrong join reorder caused by this issue.
修复当代价估算在某些极端情况下估算出 INF/NaN 非法值的问题，以及该问题发生时 join reorder 可能结果出错的问题。

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-17 09:52:19.558029898 +0000 UTC m=+950529.646832426: ☑️ agreed by winoros.
• 2024-12-17 09:53:34.256399491 +0000 UTC m=+950604.345202037: ☑️ agreed by qw4990.

[codecov]

Codecov Report

Attention: Patch coverage is 68.75000% with 5 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.1@532ca35). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.1     #56765   +/-   ##
================================================
  Coverage               ?   71.1959%           
================================================
  Files                  ?       1468           
  Lines                  ?     423743           
  Branches               ?          0           
================================================
  Hits                   ?     301688           
  Misses                 ?     101541           
  Partials               ?      20514           

Flag	Coverage Δ
unit	71.1959% <68.7500%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9656% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	41.2195% <0.0000%> (?)

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, qw4990, winoros

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [AilinKid,qw4990,winoros]
• pkg/planner/OWNERS [AilinKid,qw4990,winoros]
• pkg/statistics/OWNERS [AilinKid,qw4990,winoros]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment