Bug #110078 optimize for innodb recovery

• Submitted: 15 Feb 2023 11:52
• Modified: 15 Feb 2023 12:39
• Reporter: alex xing (OCA)
• Status: Verified
• Category: MySQL Server: InnoDB storage engine
• Severity: S5 (Performance)
• Version: 8.0.32
• OS: Any
• CPU Architecture: Any
• Tags: Contribution

[15 Feb 2023 11:52] alex xing

Description:
it is better to maintain max_lsn for recv_addr_t during parse phase.
Due to the unordered of the page flush,   there may be some pages that do not need to apply.
So we can maintain max_lsn for recv_addr_t, this reduces invalid traversal of the recv_addr->rec_list during apply phase.

How to repeat:
just read the code

Suggested fix:
maintain max_lsn for recv_addr_t during parse phase, just as the below patch

[15 Feb 2023 11:53] alex xing

a simple patch to describe the optimization

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: optimize.patch (text/plain), 1.69 KiB.

[15 Feb 2023 12:39] MySQL Verification Team

Hello Alex Xing,

Thank you for the report and contribution.

regards,
umesh