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

'alter table nocache' and then 'alter table cache', unexpected warning message #32692

Closed
tiancaiamao opened this issue Mar 1, 2022 · 1 comment · Fixed by #33358
Closed
Assignees
Labels
severity/minor sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@tiancaiamao
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

mysql> create table t (id int);
Query OK, 0 rows affected (0.01 sec)

mysql> alter table t cache;
Query OK, 1 row affected (0.01 sec)

mysql> alter table t nocache;
Query OK, 0 rows affected (0.00 sec)

mysql> alter table t cache;
Query OK, 0 rows affected, 1 warning (0.01 sec)

mysql> show warnings;
+---------+------+----------------------------------------+
| Level   | Code | Message                                |
+---------+------+----------------------------------------+
| Warning | 1062 | Duplicate entry '96' for key 'PRIMARY' |
+---------+------+----------------------------------------+
1 row in set (0.00 sec)

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

No warning message

3. What did you see instead (Required)

Unexpected warning message ... although it doesn't affect the using

4. What is your TiDB version? (Required)

master 8134942

@tiancaiamao tiancaiamao added type/bug The issue is confirmed as a bug. severity/minor labels Mar 1, 2022
@tiancaiamao
Copy link
Contributor Author

Ref #25293

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/minor sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants