Bug #108218 optimize for code
Submitted: 22 Aug 2022 9:39 Modified: 22 Aug 2022 13:07
Reporter: alex xing (OCA) Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S5 (Performance)
Version:8.0.30 OS:Any
Assigned to: CPU Architecture:Any

[22 Aug 2022 9:39] alex xing
Description:
Memory_order_acquire is placed at the last line of log_advance_ready_for_write_lsn, which doesn't seem to do anything

How to repeat:
just read the code

Suggested fix:
adjust the code
[22 Aug 2022 13:07] MySQL Verification Team
Hi Mr. xing,

Thank you for your bug report.

However, this is not a bug.

That function is called in four different places in our code, which requires that this barrier is set properly.

Not a bug.