Bug #110068 optimize for innodb recovery
Submitted: 15 Feb 2023 5:13 Modified: 15 Feb 2023 6:05
Reporter: alex xing (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S5 (Performance)
Version:8.0.31 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[15 Feb 2023 5:13] alex xing 
Description:
During innodb recovery,if space_id exist in recv_sys->missing_ids, no need to insert again.
So we can add exsit_in_missing_ids to record the situation and avoid invalid insertion logic

How to repeat:
just read the code

Suggested fix:
add exsit_in_missing_ids to record the situation and avoid invalid insertion logic,just as the below patch
[15 Feb 2023 5:13] 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.34 KiB.
[15 Feb 2023 6:05] MySQL Verification Team 
Hello Alex Xing,

Thank you for the report and contribution.

regards,
umesh