-
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
br: upgrade temporary system table #39443
Conversation
[REVIEW NOTIFICATION] This pull request has not been approved. 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. |
/component br |
f779f53
to
3fad728
Compare
3fad728
to
7dc07c4
Compare
/run-build |
Signed-off-by: zhanggaoming <gaoming.zhang@pingcap.com>
Signed-off-by: zhanggaoming <gaoming.zhang@pingcap.com>
Signed-off-by: zhanggaoming <gaoming.zhang@pingcap.com>
Signed-off-by: zhanggaoming <gaoming.zhang@pingcap.com>
Signed-off-by: zhanggaoming <gaoming.zhang@pingcap.com>
Signed-off-by: zhanggaoming <gaoming.zhang@pingcap.com>
017b031
to
0fe838e
Compare
Signed-off-by: zhanggaoming gaoming.zhang@pingcap.com
What problem does this PR solve?
Issue Number: close #38785
Problem Summary:
TiDB changed mysql.user schema in higher version
e.g.,
version95
add a columnUser_attributes
tomysql.user
version98
add a columnToken_issuer
tomysql.user
when restore 6.2.0 mysql.user to 6.4.0 will report :
Error: column count mismatch
What is changed and how it works?
Upgrade the backed up system tables before restoring to keep the schema same as the target cluster.
Check List
Tests
Side effects
Documentation
Manual Test
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.