Bug #109260 | optimize for innodb recovery | ||
---|---|---|---|
Submitted: | 1 Dec 2022 12:20 | Modified: | 3 Jan 2023 12:51 |
Reporter: | alex xing (OCA) | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
Version: | 8.0.31 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[1 Dec 2022 12:20]
alex xing
[1 Dec 2022 12:54]
MySQL Verification Team
Hi Mr. xing, Thank you for your bug report. Would you be so kind as to provide several patches which would demonstrate the optimisation. Next, have you measured the speed improvements with these changes ??? We are waiting on your feedback.
[1 Dec 2022 13:01]
alex xing
My current work just involves this part, so I pay attention to this code. If necessary, I can supplement the patch and test, but it needs to wait for some time, because I am busy for kpi recently
[1 Dec 2022 13:06]
MySQL Verification Team
Hi Mr. xing, It is OK, we can wait .....
[2 Jan 2023 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".