br: sys collation check#21306
Conversation
Signed-off-by: Jianjun Liao <jianjun.liao@outlook.com>
br/backup-and-restore-overview.md
Outdated
| > 已知问题:从 v7.2.0 版本开始,新建集群的部分系统表字段变为大小写不敏感。然而,对于从 v7.2.0 之前的版本**在线升级**到 v7.2.0 及以上版本的集群,对应的系统表字段仍然大小写敏感。如果在这两类集群之间进行包含系统表的备份和恢复操作,可能会失败。详情参见 [Issue #43717](https://github.com/pingcap/tidb/issues/43717)。 | ||
| > - 已知问题:从 v7.2.0 开始,新建集群的部分系统表字段变为大小写不敏感。然而,对于从 v7.2.0 之前的版本**在线升级**到 v7.2.0 及以上版本的集群,对应的系统表字段仍然大小写敏感。如果在这两类集群之间进行包含系统表的备份和恢复操作,可能会失败。详情参见 [Issue #43717](https://github.com/pingcap/tidb/issues/43717)。 | ||
| > | ||
| > - 从 v8.5.5 开始,如果旧集群系统表中不存在大小写冲突的记录(例如同时存在 `test.t1` 和 `test.T1`),在恢复时可以指定 BR 参数 `--sys-check-collation`。BR 会检查系统表数据在不同排序规则 (Collation) 下的兼容性:如果兼容,则可以成功恢复来自旧版本的备份;如果不兼容,则 BR 会报错并终止恢复。 |
There was a problem hiding this comment.
客户如何把你的建议落地呢?
- 如何检查大小写冲突的记录?
- 直接无脑设置 --sys-check-collation 有什么危害么?
Signed-off-by: Jianjun Liao <jianjun.liao@outlook.com>
[LGTM Timeline notifier]Timeline:
|
|
@BornChanger: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this: 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-sigs/prow repository. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hfxsd The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
In response to a cherrypick label: new pull request created to branch |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?