From 3fe99388ed0b1d23a54b2bfae855b3f2f9ea3fd9 Mon Sep 17 00:00:00 2001 From: Yasuo Honda Date: Wed, 16 Sep 2026 15:05:57 +0900 Subject: [PATCH] docs: fix illogical "rarely truncated" wording for HASH/KEY partitioned tables Hash and Key partitioned tables do not support DROP PARTITION at all, so framing this as "these partitions are rarely truncated" misstates the limitation as a matter of frequency rather than a hard unsupported-operation constraint. Reworded to state the trade-off does not apply to these tables, rather than implying dropping is just uncommon. Found while reviewing the Japanese translation of this file, which faithfully mirrored this EN wording; flagged by a CodeRabbit review on the JA translation PR. Co-Authored-By: Claude Sonnet 5 --- best-practices/tidb-partitioned-tables-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/best-practices/tidb-partitioned-tables-best-practices.md b/best-practices/tidb-partitioned-tables-best-practices.md index b682dff04dc28..f6c798a40bcf6 100644 --- a/best-practices/tidb-partitioned-tables-best-practices.md +++ b/best-practices/tidb-partitioned-tables-best-practices.md @@ -430,7 +430,7 @@ Before you use partitioned tables, consider the following limitations: SELECT * FROM server_info WHERE `serial_no` = ?; ``` -- To reduce scan overhead for queries that do not use the partition key, you need to create a global index. Although global indexes can slow down `DROP PARTITION` operations, Hash and Key partitioned tables do not support `DROP PARTITION`. Therefore, global indexes are a practical solution because these partitions are rarely truncated. For example: +- To reduce scan overhead for queries that do not use the partition key, you need to create a global index. Although global indexes can slow down `DROP PARTITION` operations, Hash and Key partitioned tables do not support `DROP PARTITION` at all, so this trade-off does not apply to them. Therefore, global indexes are a practical solution for these tables. For example: ```sql ALTER TABLE server_info ADD UNIQUE INDEX(serial_no, id) GLOBAL;