Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

statistics: remove dead code (#58412) #58442

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #58412

Signed-off-by: Rustin170506 techregister@pm.me

What problem does this PR solve?

Issue Number: ref #57804

Problem Summary:

What changed and how does it work?

In this PR, I removed the dead code. The stats loading for the PK, as shown, has never been executed, so it is safe to remove.

Some background:

  1. statistics: fix PK column TopN not loading when init stats #37552 This PR tried to load it correctly.
  2. statistics: fix wrong behavior for primary key' non-lite init stats #53298 This PR decided to remove it at all.
  3. Another fix based on the previous PR: *: not load unnecessay data during the non-lite-init-stats #53399
  4. Another full rewrite: statistics: correct behavior of non-lite InitStats and stats sync load of no stats column #57803

So we just forgot to delete it.

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

Signed-off-by: Rustin170506 <techregister@pm.me>
Signed-off-by: Rustin170506 <techregister@pm.me>
Signed-off-by: Rustin170506 <techregister@pm.me>
Signed-off-by: Rustin170506 <techregister@pm.me>
@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. sig/planner SIG: Planner size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. labels Dec 20, 2024
@ti-chi-bot ti-chi-bot mentioned this pull request Dec 20, 2024
13 tasks
Copy link

codecov bot commented Dec 20, 2024

Codecov Report

Attention: Patch coverage is 88.88889% with 2 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.5@02bdc2b). Learn more about missing BASE report.

Additional details and impacted files
@@               Coverage Diff                @@
##             release-8.5     #58442   +/-   ##
================================================
  Coverage               ?   57.0274%           
================================================
  Files                  ?       1773           
  Lines                  ?     627787           
  Branches               ?          0           
================================================
  Hits                   ?     358011           
  Misses                 ?     245613           
  Partials               ?      24163           
Flag Coverage Δ
integration 37.0114% <11.1111%> (?)
unit 72.6532% <88.8888%> (?)

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

Components Coverage Δ
dumpling 52.8711% <0.0000%> (?)
parser ∅ <0.0000%> (?)
br 52.2984% <0.0000%> (?)

Copy link
Member

@Rustin170506 Rustin170506 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! :shipit:

@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Dec 23, 2024
Copy link
Contributor

@fixdb fixdb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Dec 23, 2024
Copy link

ti-chi-bot bot commented Dec 23, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-12-23 04:14:56.462708226 +0000 UTC m=+1448686.551510764: ☑️ agreed by Rustin170506.
  • 2024-12-23 04:16:14.788834614 +0000 UTC m=+1448764.877637156: ☑️ agreed by fixdb.

Copy link
Contributor

@elsa0520 elsa0520 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

ti-chi-bot bot commented Dec 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elsa0520, fixdb, Rustin170506

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:

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

@Rustin170506
Copy link
Member

/test all

Copy link

tiprow bot commented Dec 23, 2024

@Rustin170506: No presubmit jobs available for pingcap/tidb@release-8.5

In response to this:

/test all

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.

@ti-chi-bot ti-chi-bot bot merged commit d38383a into pingcap:release-8.5 Dec 23, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. lgtm release-note-none Denotes a PR that doesn't merit a release note. sig/planner SIG: Planner size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants