Bug #100186 | some useless latch on Btree search and modify path | ||
---|---|---|---|
Submitted: | 11 Jul 2020 21:16 | Modified: | 17 Aug 2020 12:09 |
Reporter: | Zongzhi Chen (OCA) | 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 |
[11 Jul 2020 21:16]
Zongzhi Chen
[13 Jul 2020 12:56]
MySQL Verification Team
Hi Mr. zongzhi, Thank you for your bug report. You wrote that a test can prove an unnecessary latch lock. Can you send us that simple test case ??? Thanks in advance.
[14 Jul 2020 16:57]
Zongzhi Chen
simple test such as oltp_read_write can trigger unnecessary latch. Actually, every SMO(struct modify operation) will cause the father node unnecessary latch, however, as what I said before, since InnoDB's rw_lock support recursion add lock, it won't cause deadlock issue.. If you want get the information, you need print the latch information before the code..
[15 Jul 2020 12:49]
MySQL Verification Team
Hi Mr. zongzhi, Can you provide us with a proper patch for 8.0.21 that will show the problem ??? Also, have you prepared a patch for this bug, even an ancillary one ??? Both would be welcome.
[16 Aug 2020 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".
[17 Aug 2020 12:09]
MySQL Verification Team
We can't repeat this bug report. Furthermore, we can do without a test case if the report contained a fully detailed code analysis. Some benchmarks would be welcome, as well as a patch, which would allow us to verify this report, without any test case.