*: not load unnecessay data during the non-lite-init-stats

[hawkingrei]

What problem does this PR solve?

Issue Number: close #53425

Problem Summary:

What changed and how does it work?

After #53298, We know that TiDB cannot load the topn when to init stats and have to load it when to sync load. so we need not load hists for the not-index column when to init stats.

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

All modified and coverable lines are covered by tests ✅

Project coverage is 74.6174%. Comparing base (68219b9) to head (e876856).
Report is 20 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53399        +/-   ##
================================================
+ Coverage   72.5268%   74.6174%   +2.0906%     
================================================
  Files          1505       1505                
  Lines        429830     431474      +1644     
================================================
+ Hits         311742     321955     +10213     
+ Misses        98799      89587      -9212     
- Partials      19289      19932       +643     

Flag	Coverage Δ
integration	49.1528% <0.0000%> (?)
unit	71.3514% <100.0000%> (-0.0676%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	50.3858% <ø> (+8.9818%)	⬆️

[hawkingrei]

initStatsHistograms4ChunkConcurrency is the same as initStatsHistograms4Chunk. But it will not read is_index.

[Rustin170506]

What do you mean by concurrency? Can we just add a parameter to initStatsHistograms4Chunk to avoid copying the code?

[hawkingrei]

concurrency means it is in concurrency mode.

It is hard that their code is not aligned.

[hawkingrei]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hi-rustin, 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/planner/OWNERS [hi-rustin,qw4990]
• pkg/statistics/OWNERS [hi-rustin,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-05-22 06:52:23.874528321 +0000 UTC m=+2240897.631663892: ☑️ agreed by hi-rustin.
• 2024-05-22 09:59:23.051951515 +0000 UTC m=+2252116.809087088: ☑️ agreed by qw4990.

[hawkingrei]

/cherrypick release-7.5

[hawkingrei]

/cherrypick release-8.1

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-7.5: #53491.

In response to this:

/cherrypick release-7.5

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 ti-community-infra/tichi repository.

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-8.1: #53492.

In response to this:

/cherrypick release-8.1

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 ti-community-infra/tichi repository.

[ti-chi-bot]

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

[ti-chi-bot]

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