Skip to content
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

delete range of drop index for partition table is not correct. #33620

Closed
wjhuang2016 opened this issue Mar 31, 2022 · 0 comments · Fixed by #33726
Closed

delete range of drop index for partition table is not correct. #33620

wjhuang2016 opened this issue Mar 31, 2022 · 0 comments · Fixed by #33726
Assignees
Labels
affects-4.0 This bug affects 4.0.x versions. affects-5.0 This bug affects 5.0.x versions. affects-5.1 This bug affects 5.1.x versions. affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. affects-5.4 This bug affects 5.4.x versions. affects-6.0 component/tablepartition This issue is related to Table Partition of TiDB. severity/major sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.

Comments

@wjhuang2016
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

mysql> create table t (id int, c1 int, c2 int, primary key(id), key i1(c1), key i2(c2)) partition by range(id) (partition p0 values less than (6), partition p01 values less than (10) , partition p1 values less than maxvalue);
Query OK, 0 rows affected (0.01 sec)

mysql> alter table t  drop index i1;
Query OK, 0 rows affected (0.02 sec)

mysql> select * from mysql.gc_delete_range_done;
+--------+------------+----------------------------------------+----------------------------------------+--------------------+
| job_id | element_id | start_key                              | end_key                                | ts                 |
+--------+------------+----------------------------------------+----------------------------------------+--------------------+
|    147 |          2 | 74800000000000008f5f698000000000000002 | 74800000000000008f5f698000000000000003 | 432199516397240321 |
+--------+------------+----------------------------------------+----------------------------------------+--------------------+
1 row in set (0.00 sec)

2. What did you expect to see? (Required)

3 rows in gc_delete_range_done

3. What did you see instead (Required)

only 1 row.

4. What is your TiDB version? (Required)

master

@wjhuang2016 wjhuang2016 added type/bug The issue is confirmed as a bug. severity/major affects-4.0 This bug affects 4.0.x versions. affects-5.0 This bug affects 5.0.x versions. affects-5.1 This bug affects 5.1.x versions. affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. affects-5.4 This bug affects 5.4.x versions. affects-6.0 sig/sql-infra SIG: SQL Infra labels Mar 31, 2022
@mjonss mjonss added the component/tablepartition This issue is related to Table Partition of TiDB. label Mar 31, 2022
@wjhuang2016 wjhuang2016 self-assigned this Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.0 This bug affects 4.0.x versions. affects-5.0 This bug affects 5.0.x versions. affects-5.1 This bug affects 5.1.x versions. affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. affects-5.4 This bug affects 5.4.x versions. affects-6.0 component/tablepartition This issue is related to Table Partition of TiDB. severity/major sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants