br/restore: fixed restore sys tables

[YuJuncen]

Signed-off-by: hillium [email protected]

What problem does this PR solve?

Issue Number: close #38538

Problem Summary:

What is changed and how it works?

After this PR, we would give up for keeping table ID if table ID is greater than MaxUInt32.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

- [ ] No code

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

(This bug was introduced only in the master branch.)

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• 3pointer
• fengou1

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[lance6716]

If the cluster to be restored has the same version with backup cluster, we might let itself create the special tables. Because the table ID for these tables are hardcoded in TiDB, restore them to another table ID may cause problems.

When the cluster version is different, these tables has no effects and no need to be restored.

[YuJuncen]

@lance6716 Yep, but once the user wants to restore mysql.*, we would try to restore those tables and we are going to try to advance the global ID to the insane ID, which leads to a failed restoration.

[fengou1]

ship it

[YuJuncen]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: ba1056b

[ti-chi-bot]

@YuJuncen: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.