planner, stats: overflow estimation may lead to wrong join reorder

[winoros]

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 可能结果出错的问题。

[codecov]

Codecov Report

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

Project coverage is 56.3836%. Comparing base (dfd6cf2) to head (d0232c1).
Report is 7 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56752         +/-   ##
=================================================
- Coverage   73.3217%   56.3836%   -16.9382%     
=================================================
  Files          1631       1784        +153     
  Lines        451083     641229     +190146     
=================================================
+ Hits         330742     361548      +30806     
- Misses       100025     254985     +154960     
- Partials      20316      24696       +4380     

Flag	Coverage Δ
integration	37.9788% <70.5882%> (?)
unit	72.4424% <47.0588%> (-0.0028%)	⬇️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	52.6981% <ø> (+6.6655%)	⬆️

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-10-21 16:00:43.766823618 +0000 UTC m=+280444.463614246: ☑️ agreed by time-and-fate.
• 2024-10-22 03:07:29.184930158 +0000 UTC m=+320449.881720781: ☑️ agreed by hawkingrei.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, hawkingrei, time-and-fate

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,hawkingrei,time-and-fate]
• pkg/planner/OWNERS [AilinKid,hawkingrei,time-and-fate]
• pkg/statistics/OWNERS [AilinKid,hawkingrei,time-and-fate]

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

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #56763.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #56764.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #56765.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.4: #56766.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #56767.