Bug #103620 | No need to acquire shard mutex if setting to O_DIRECT_NO_FSYNC | ||
---|---|---|---|
Submitted: | 7 May 2021 8:31 | Modified: | 8 May 2021 3:48 |
Reporter: | zhai weixiang (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 8.0.24 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[7 May 2021 8:31]
zhai weixiang
[7 May 2021 9:38]
MySQL Verification Team
Hello Zhai, Thank you for the report and feedback. regards, Umesh
[7 May 2021 16:21]
Sunny Bains
The flush method is a dynamic variable therefore we cannot assume that this will always hold.
[8 May 2021 3:48]
zhai weixiang
Hi, Sunny, I checked the code, it's readonly ! static MYSQL_SYSVAR_ENUM(flush_method, innodb_flush_method, PLUGIN_VAR_RQCMDARG | PLUGIN_VAR_READONLY, "With which method to flush data", nullptr, nullptr, 0, &innodb_flush_method_typelib);