Bug #109981 optimize for innodb recovery

• Submitted: 8 Feb 2023 9:15
• Modified: 10 Mar 2023 13:29
• Reporter: alex xing (OCA)
• Status: Not a Bug
• Category: MySQL Server: InnoDB storage engine
• Severity: S5 (Performance)
• Version: 8.0.31
• OS: Any
• CPU Architecture: Any

[8 Feb 2023 9:15] alex xing

Description:
During the period of innodb recovery, need to repeatedly check whether the undo space is truncate,which slows down the recovery.

Call stack as follows：
fil_tablespace_open_for_recovery
|--> Fil_system::open_for_recovery
|  |--> Fil_system::ibd_open_for_recovery
|  |  |--> is_active_truncate_log_present

I think some relevant marks can be made in recv_sys to prevent repeated checks. 

How to repeat:
just read the code

Suggested fix:
I think some relevant marks can be made in recv_sys to prevent repeated checks.

[8 Feb 2023 13:05] MySQL Verification Team

Hi Mr. xing,

Thank you for reporting a performance improvement request.

However, your description is very rudimentary and unclear. It also does not contain all necessary details.

Since you are contributing code, the best course of action would be to send us a patch.

We are waiting on your full feedback.

[10 Mar 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".