Bug #96239 | Undo might not cleanup entries of innodb_ddl_log due to exception | ||
---|---|---|---|
Submitted: | 17 Jul 2019 20:39 | Modified: | 27 Aug 2019 12:12 |
Reporter: | tony zhou | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | auto_inc, crash, undo |
[17 Jul 2019 20:39]
tony zhou
[26 Jul 2019 12:12]
MySQL Verification Team
Hello Mr. Zhou, Thank you for your bug report. We do need some more answers and explanations from you, before we proceed ....... First of all, what do you mean "reboot the server" ??? Re-start MySQL server or reboot the OS. The OS that I use is rebooted by properly closing everything. I do not intend to turn the computer off, since it might have bad consequences for my machine. Next, when you write that primary key is correctly removed and secondary index has some entries left, please let us know the procedure on how can we determine that ..... Next, how can we determine that auto-increment index is messed up ???? Thanks in advance.
[27 Aug 2019 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".