Bug #106238 | Wrong FIL_PAGE_LSN set during crash recovery | ||
---|---|---|---|
Submitted: | 21 Jan 2022 16:59 | Modified: | 24 Jan 2022 14:11 |
Reporter: | Kang Wang | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
Version: | All | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[21 Jan 2022 16:59]
Kang Wang
[24 Jan 2022 13:53]
MySQL Verification Team
Hi Mr. Wang, Thank you for your bug report. However, we do need the exact release of 8.0 in which this error occurs. Also, what are the consequences of this error ???? Last but not least, is there any way that we can reproduce this problem.
[24 Jan 2022 14:11]
MySQL Verification Team
Hi Mr. Wang, This is also to inform you that in the latest release of 8.0, there is no more local end_lsn. There is an end_lsn in a separate block, which does not apply to the block that you are referring to: if (recv->start_lsn >= page_lsn ) { lsn_t end_lsn; if (!modification_to_page) { modification_to_page = true; start_lsn = recv->start_lsn; } Hence, the above end_lsn does not apply to the code below it, where the end_lsn from the upper block is the only one that is used. Hence, this is not a bug.