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.

Sign up for GitHub

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

Jump to bottom

BR: 6.2.0 system table mysql.user can't be restored to 6.4.0 #38785

Closed
seiya-annie opened this issue Nov 1, 2022 · 2 comments · Fixed by #39460
Closed

BR: 6.2.0 system table mysql.user can't be restored to 6.4.0 #38785

seiya-annie opened this issue Nov 1, 2022 · 2 comments · Fixed by #39460
Assignees
@3pointer
Labels
affects-6.2 affects-6.3 affects-6.4 compatibility-breaker Violation of forwards/backwards compatibility in a design-time piece. component/br This issue is related to BR of TiDB. severity/critical type/bug The issue is confirmed as a bug.

Comments

@seiya-annie
Copy link

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

tidb changed mysql.user schema in 6.4.0
version95 add a column User_attributes to mysql.user
version98 add a column Token_issuer to mysql.user

when restore 6.2.0 mysql.user to 6.4.0 will report :
Error: column count mismatch, table: user, col in cluster: 38, col in backup: 37: [BR:Restore:ErrR

2. What did you expect to see? (Required)

restore success

3. What did you see instead (Required)

Error: column count mismatch, table: user, col in cluster: 38, col in backup: 37: [BR:Restore:ErrR

4. What is your TiDB version? (Required)

master
@seiya-annie seiya-annie added type/bug The issue is confirmed as a bug. component/br This issue is related to BR of TiDB. severity/moderate labels Nov 1, 2022
@IANTHEREAL IANTHEREAL added the compatibility-breaker Violation of forwards/backwards compatibility in a design-time piece. label Nov 1, 2022
@IANTHEREAL
Copy link
Contributor

IANTHEREAL commented Nov 1, 2022 •
edited
Loading

@bb7133 Hi, do you know who can help with this modification(mysql.user schema change)?

@seiya-annie
Copy link
Author

@wjhuang2016 PTAL

@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 may-affects-6.4 labels Nov 15, 2022
This was referenced Nov 29, 2022
Closed
Merged
@3pointer 3pointer removed may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-6.0 may-affects-6.1 labels Nov 30, 2022
ti-chi-bot pushed a commit that referenced this issue Dec 1, 2022
@MoCuishle28
br: skip compatibility check for the mysql.user table when restoring (#…
d3f7ec0 
…39460)

close #38785
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@3pointer 3pointer

Labels
affects-6.2 affects-6.3 affects-6.4 compatibility-breaker Violation of forwards/backwards compatibility in a design-time piece. component/br This issue is related to BR of TiDB. severity/critical type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
5 participants
@jebter @3pointer @IANTHEREAL @seiya-annie @ti-chi-bot