-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
executor: track the memory usage for building range in IndexLookUpExecutor | tidb-test=2eb0d03843bfec7539602dada4f96ea2ee982c0e #56441
executor: track the memory usage for building range in IndexLookUpExecutor | tidb-test=2eb0d03843bfec7539602dada4f96ea2ee982c0e #56441
Conversation
Hi @wshwsh12. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with 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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-8.3-20240927-v8.3.0 #56441 +/- ##
================================================================
Coverage ? 74.7888%
================================================================
Files ? 1576
Lines ? 440674
Branches ? 0
================================================================
Hits ? 329575
Misses ? 90867
Partials ? 20232
Flags with carried forward coverage won't be shown. Click here to find out more.
|
/hold |
/unhold |
[LGTM Timeline notifier]Timeline:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: XuHuaiyu 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 |
726da9c
into
pingcap:release-8.3-20240927-v8.3.0
What problem does this PR solve?
Issue Number: close #56440
Problem Summary:
What changed and how does it work?
Check List
Tests
Test the case in issue 56440, the sql can be killed.
See the slow log, the sql track 1GB and killed.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.