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: fix puting wrong stats into cache (#52421) #52422

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #52421

What problem does this PR solve?

Issue Number: close #52419

Problem Summary:

What changed and how does it work?

We put the wrong table id as key to write stats cache

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: Weizhen Wang <wangweizhen@pingcap.com>
Signed-off-by: Weizhen Wang <wangweizhen@pingcap.com>
Signed-off-by: Weizhen Wang <wangweizhen@pingcap.com>
Copy link

codecov bot commented Apr 8, 2024

Codecov Report

❗ No coverage uploaded for pull request base (release-7.5@a44d7a9). Click here to learn what that means.
The diff coverage is 100.0000%.

Additional details and impacted files
@@               Coverage Diff                @@
##             release-7.5     #52422   +/-   ##
================================================
  Coverage               ?   71.9881%           
================================================
  Files                  ?       1410           
  Lines                  ?     409416           
  Branches               ?          0           
================================================
  Hits                   ?     294731           
  Misses                 ?      94850           
  Partials               ?      19835           
Flag Coverage Δ
unit 71.9881% <100.0000%> (?)

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

Components Coverage Δ
dumpling 53.9913% <0.0000%> (?)
parser ∅ <0.0000%> (?)
br 53.3457% <0.0000%> (?)

@ti-chi-bot ti-chi-bot bot added the lgtm label Apr 9, 2024
Copy link

ti-chi-bot bot commented Apr 9, 2024

[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:

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

Copy link

ti-chi-bot bot commented Apr 9, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-04-08 14:49:40.017356268 +0000 UTC m=+887441.544896812: ☑️ agreed by winoros.
  • 2024-04-09 02:59:48.234036317 +0000 UTC m=+931249.761576862: ☑️ agreed by hawkingrei.

@ti-chi-bot ti-chi-bot added the cherry-pick-approved Cherry pick PR approved by release team. label Apr 9, 2024
@ti-chi-bot ti-chi-bot bot merged commit 428670a into pingcap:release-7.5 Apr 9, 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 size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-7.5
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants