Bug #105246 it is better to execute dict_persist_init() after judge the err
Submitted: 18 Oct 2021 7:20 Modified: 18 Oct 2021 7:41
Reporter: alex xing (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S5 (Performance)
Version:8.0.26 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[18 Oct 2021 7:20] alex xing 
Description:
in srv_start, it is better to execute dict_persist_init() after judge the err returned by srv_sys_space.open_or_create
because if err!=DB_SUCCESS , the func just return, so need to execute dict_persist_init.

How to repeat:
just read the code

Suggested fix:
execute dict_persist_init() after judge the err returned by srv_sys_space.open_or_create  just as the below patch
[18 Oct 2021 7:21] 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), 993 bytes.
[18 Oct 2021 7:41] MySQL Verification Team 
Hello Alex Xing,

Thank you for the report and contribution.

regards,
Umesh