-
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
planner: logically delete the bindinfo when create the new binding #26015
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/label sig/planner, epic/sql-plan-management, type/bug-fix |
/cc @eurekaka |
This small PR lasted for 10 days, please review it in time. |
@Reminiscent: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
rows = tk.MustQuery("select original_sql, status from mysql.bind_info").Rows() | ||
c.Assert(len(rows), Equals, 2) | ||
c.Assert(rows[0][1], Equals, "deleted") | ||
c.Assert(rows[1][1], Equals, "using") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the builtin
row not returned by this query?
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 2d207da
|
/run-all-tests |
1 similar comment
/run-all-tests |
/run-cherry-picker release-5.0 |
/run-cherry-picker release-5.1 |
cherry pick to release-5.1 in PR #32901 |
Signed-off-by: ti-srebot <[email protected]>
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-5.0 in PR #32902 |
What problem does this PR solve?
Issue Number: close #25842
Problem Summary:
In this PR, we physically delete the bindings when we create a new binding to prevent some problems of inconsistent cache. But this method can not solve all the problems, for example issue#25842. So after we introduce the table lock for
mysql.bind_info
in this PR, we can revert the origin change.What is changed and how it works?
What's Changed:
Logically delete the binding when we create a new binding.
Check List
Tests
Release note