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

sequence negative cache size will cause TiDB server panic #17945

Closed
wjhuang2016 opened this issue Jun 11, 2020 · 0 comments · Fixed by #18071
Closed

sequence negative cache size will cause TiDB server panic #17945

wjhuang2016 opened this issue Jun 11, 2020 · 0 comments · Fixed by #18071
Assignees
Labels
severity/major 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 sequence se INCREMENT -9223372036854775807 cache -1;
Query OK, 0 rows affected (0.00 sec)

mysql> select nextval(se);
+-------------+
| nextval(se) |
+-------------+
|          -1 |
+-------------+
1 row in set (0.00 sec)

mysql> select nextval(se);
^C^C -- query aborted
^C^C -- query aborted

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

3. What did you see instead (Required)

4. Affected version (Required)

master

5. Root Cause Analysis

@wjhuang2016 wjhuang2016 added the type/bug The issue is confirmed as a bug. label Jun 11, 2020
@AilinKid AilinKid changed the title nextval() casuse TiDB server panic sequence negative cache size will cause TiDB server panic Jun 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants