Skip to content

docs: fix illogical wording for HASH/KEY partitioned tables and DROP PARTITION #23892

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

Open
yahonda wants to merge 1 commit into
base: release-8.5
Choose a base branch
from
Open

docs: fix illogical wording for HASH/KEY partitioned tables and DROP PARTITION #23892

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion best-practices/tidb-partitioned-tables-best-practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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;
Expand Down