infoschema, planner: lock the new table id in tryLockMDLAndUpdateSchemaIfNecessary #39366
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: wjhuang2016 <[email protected]>
|
[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. |
ti-chi-bot
added
release-note-none
lcwangchao
approved these changes
Nov 24, 2022
|
/run-mysql-test |
2 similar comments
|
/run-mysql-test |
|
/run-mysql-test |
tangenta
approved these changes
Nov 25, 2022
ti-chi-bot
added
status/LGT2
|
/merge |
|
This pull request has been accepted and is ready to merge. Commit hash: f303c4f
|
ti-chi-bot
added
the
status/can-merge
TiDB MergeCI notify✅ Well Done! New fixed [1] after this pr merged.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: wjhuang2016 [email protected]
What problem does this PR solve?
Issue Number: close #39363
Problem Summary:
For truncating a table, If loading the domain schema in tryLockMDLAndUpdateSchemaIfNecessary(), the new table id is different from the old one. So we need to lock the new one, otherwise, it may update the schema again if call tryLockMDLAndUpdateSchemaIfNecessary() again.
Tests
Run the schrDDL test without the previous error.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.