Bug #106249 it is better to use trx_undo_get_next_rec_from_next_page

• Submitted: 23 Jan 2022 3:58
• Modified: 23 Jan 2022 9:54
• Reporter: alex xing (OCA)
• Status: Verified
• Category: MySQL Server: InnoDB storage engine
• Severity: S5 (Performance)
• Version: 8.0
• OS: Any
• CPU Architecture: Any
• Tags: Contribution

[23 Jan 2022 3:58] alex xing

Description:
The native logic use trx_undo_get_next_rec to get undo_rec which calls trx_undo_page_get_next_rec one more time.
So it is better to use trx_undo_get_next_rec_from_next_page directly

How to repeat:
just read the code

Suggested fix:
optimize as the below patch

[23 Jan 2022 3:59] alex xing

a simple patch based on  8.0.19.  The same may be true for the latest version of the code.

(*) 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), 2.35 KiB.

[23 Jan 2022 9:54] MySQL Verification Team

Hello Alex Xing,

Thank you for the report and contribution.

regards,
Umesh