statistics: make sure PQ can analyze all indexes with stats version 1

[Rustin170506]

What problem does this PR solve?

Issue Number: close #57257

Problem Summary:

What changed and how does it work?

After switching to the new PQ, we only have one chance to analyze newly added indexes. For example, if two indexes are created in a very short period and the analyze version 1 is used, we need to analyze these indexes separately.

However, with the current implementation, we only analyze one index at a time, which means the second index will be missed.

In this PR, I’ve checked the analyze version to ensure proper handling. The lower versions don’t have this issue because we can analyze the second index after rebuilding the entire priority queue.

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.

None

[codecov]

Codecov Report

Attention: Patch coverage is 34.61538% with 17 lines in your changes missing coverage. Please review.

Project coverage is 73.7087%. Comparing base (426ce3e) to head (d020a52).
Report is 8 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57258        +/-   ##
================================================
+ Coverage   72.9810%   73.7087%   +0.7276%     
================================================
  Files          1660       1690        +30     
  Lines        458645     466664      +8019     
================================================
+ Hits         334724     343972      +9248     
+ Misses       103364     101490      -1874     
- Partials      20557      21202       +645     

Flag	Coverage Δ
integration	46.2485% <0.0000%> (?)
unit	72.3364% <34.6153%> (+0.0056%)	⬆️

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

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	45.0481% <ø> (-0.0063%)	⬇️

[elsa0520]

LGTM

[elsa0520]

/hold

[Rustin170506]

/unhold

[Rustin170506]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elsa0520, qw4990

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:

• pkg/statistics/OWNERS [elsa0520,qw4990]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-11-11 03:23:44.518560886 +0000 UTC m=+240186.709429884: ☑️ agreed by elsa0520.
• 2024-11-11 06:23:13.578582246 +0000 UTC m=+250955.769451242: ☑️ agreed by qw4990.

[Rustin170506]

@ti-chi-bot Wake up

[ti-chi-bot]

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

[ti-chi-bot]

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