-
Notifications
You must be signed in to change notification settings - Fork 1.2k
refine modify column #21110
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
base: master
Are you sure you want to change the base?
refine modify column #21110
Conversation
Signed-off-by: wjhuang2016 <[email protected]>
|
add the do-not-merge/hold label as the change in this PR won't be included in v8.5.4 |
Co-authored-by: Ruihao Chen <[email protected]> Co-authored-by: Grace Cai <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
|
||
| > **注意:** | ||
| > | ||
| > 当 `VARCHAR` 转换为 `CHAR` 时,要求所有原数据的末尾均不包含空格;若不满足该条件,TiDB 仍会执行 Reorg-Data。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| > 当 `VARCHAR` 转换为 `CHAR` 时,要求所有原数据的末尾均不包含空格;若不满足该条件,TiDB 仍会执行 Reorg-Data。 | |
| > 当 `VARCHAR` 转换为 `CHAR` 时,要求所有原数据的末尾均不包含空格;若不满足该条件,TiDB 仍会执行 Reorg Data,以保持数据一致性。 |
| - `DECIMAL` 精度修改 | ||
| - 从 `VARCHAR(10)` 到 `VARCHAR(5)` 的长度压缩 | ||
|
|
||
| 从 v8.5.5 和 v9.0.0 版本起,TiDB 优化了部分 Reorg-Data 类型变更的执行效率。在 [SQL 模式](/sql-mode.md)严格模式(即 `sql_mode` 值包含 `STRICT_TRANS_TABLES` 或 `STRICT_ALL_TABLES`),以下类型变更将不再进行表数据重建,只进行部分索引的重建: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 从 v8.5.5 和 v9.0.0 版本起,TiDB 优化了部分 Reorg-Data 类型变更的执行效率。在 [SQL 模式](/sql-mode.md)严格模式(即 `sql_mode` 值包含 `STRICT_TRANS_TABLES` 或 `STRICT_ALL_TABLES`),以下类型变更将不再进行表数据重建,只进行部分索引的重建: | |
| 从 v8.5.5 和 v9.0.0 版本起,TiDB 优化了部分 Reorg-Data 类型变更的执行效率。在 [SQL 模式](/sql-mode.md)严格模式(即 `sql_mode` 值包含 `STRICT_TRANS_TABLES` 或 `STRICT_ALL_TABLES`),在进行以下类型变更时,TiDB 将不再进行表数据重建,只进行部分索引的重建: |
| - 从 `VARCHAR` 转换为 `BIGINT` | ||
| - `DECIMAL` 精度修改 | ||
| - 从 `VARCHAR(10)` 到 `VARCHAR(5)` 的长度压缩 | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Reorg-Data 指的是在修改列类型时,TiDB 需要对表中的现有数据进行重建,包括读取原数据,按照新的数据格式进行处理,然后重新写入表中。这类操作通常比较耗时,时间消耗与表中的数据量成正比。 | |
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?