statistics/handle: refine the condition of dumping stats delta (#41133)

[ti-chi-bot]

This is an automated cherry-pick of #41133

What problem does this PR solve?

Issue Number: ref #38189 ref #36004 ref #39785

Problem Summary:

What is changed and how it works?

Refine the condition of dumping stats delta:

1. If the table doesn't exist or is a mem table or system table, then return false.
2. If the mode is DumpAll, then return true.
3. If the stats delta haven't been dumped in the past hour, then return true.
4. If the table stats is pseudo or empty or Modify Count / Table Count exceeds the threshold.

There are two changes(marked in bold):

1. a mem table or system table: It can prevent the cases such as Continuously update the stats_meta of mysql.tidb in auto analyze loop #39785.
2. pseudo: When we fail to create stats meta after creating a table, ddl, statistics: fix stats meta missing when creating many tables at once #38301 uses the dump stats delta procedure to fill in missing stats meta. However, in that case, the table's stats is pseudo and the old condition would refuse to dump stats delta. So we need the change to fill in missing stats meta completely.

Check List

Tests

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

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

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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/test-infra repository.

[ti-chi-bot]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev	075eea2	link	true	/test check-dev
idc-jenkins-ci-tidb/build	075eea2	link	true	/test build
idc-jenkins-ci-tidb/unit-test	075eea2	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev_2	075eea2	link	true	/test check-dev2
idc-jenkins-ci-tidb/mysql-test	075eea2	link	true	/test mysql-test

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.