statistics: update stats_history table when it meets duplicate

[Defined2014]

What problem does this PR solve?

Issue Number: close #47539

Problem Summary:

What changed and how does it work?

Check List

Tests

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

run SQLs below, no warning msg again.

set tidb_analyze_version = 1;
set tidb_enable_global_index = true;
set global tidb_enable_historical_stats = true;

CREATE TABLE t ( a int, b int, c int default 0)
  PARTITION BY RANGE (a) (
  PARTITION p0 VALUES LESS THAN (10),
  PARTITION p1 VALUES LESS THAN (20),
  PARTITION p2 VALUES LESS THAN (30),
  PARTITION p3 VALUES LESS THAN (40));
INSERT INTO t(a, b) values(1, 1), (2, 2), (3, 3), (15, 15), (25, 25), (35, 35);
ALTER TABLE t ADD UNIQUE INDEX idx(b);
analyze table t;

• 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

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @Defined2014. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[hawkingrei]

/ok-to-test

[codecov]

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 56.4875%. Comparing base (08b7ac6) to head (de8cd7f).
Report is 41 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54315         +/-   ##
=================================================
- Coverage   74.7550%   56.4875%   -18.2676%     
=================================================
  Files          1522       1649        +127     
  Lines        361455     617885     +256430     
=================================================
+ Hits         270206     349028      +78822     
- Misses        71616     245479     +173863     
- Partials      19633      23378       +3745     

Flag	Coverage Δ
integration	37.0528% <0.0000%> (?)
unit	71.7993% <75.0000%> (-1.8477%)	⬇️

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

Components	Coverage Δ
dumpling	52.9656% <ø> (-2.2339%)	⬇️
parser	∅ <ø> (∅)
br	52.7422% <ø> (+4.8112%)	⬆️

[Defined2014]

/retest

[Defined2014]

/retest

[hawkingrei]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, 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:

• pkg/statistics/OWNERS [hawkingrei,winoros]

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-06-29 00:53:42.393641872 +0000 UTC m=+1026548.879130706: ☑️ agreed by hawkingrei.
• 2024-07-01 06:42:41.874967625 +0000 UTC m=+1220288.360456464: ☑️ agreed by winoros.

[qw4990]

/cherry-pick release-7.5

[ti-chi-bot]

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

[ti-chi-bot]

@qw4990: new pull request could not be created: failed to create pull request against pingcap/tidb#release-7.5 from head ti-chi-bot:cherry-pick-54315-to-release-7.5: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-54315-to-release-7.5."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherry-pick 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.