Bug #117961 --flush only affects MyISAM storage engine, but RefMan doesn't describe it

• Submitted: 13 Apr 9:26
• Modified: 14 Apr 19:39
• Reporter: Tsubasa Tanaka (OCA)
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 8.0, 8.4, 9.2
• OS: Any
• CPU Architecture: Any

[13 Apr 9:26] Tsubasa Tanaka

Description:
Document describes --flush as

```
If ON, the server flushes (synchronizes) all changes to disk after each SQL statement. Normally, MySQL does a write of all changes to disk only after each SQL statement and lets the operating system handle the synchronizing to disk. See Section B.3.3.3, “What to Do If MySQL Keeps Crashing”. This variable is set to ON if you start mysqld with the --flush option.
```

It seems to affect whole MySQL server processing, but actually --flush only affects MyISAM storage engine, 

- --flush is handled as `myisam_flush` variable
  - https://github.com/mysql/mysql-server/blob/mysql-8.4.4/sql/sys_vars.cc#L2152-L2154 

- And `myisam_flush` is only used at storage/myisam
  - https://github.com/search?q=repo%3Amysql%2Fmysql-server%20myisam_flush&type=code

How to repeat:
See document described for --flush

https://dev.mysql.com/doc/refman/9.2/en/server-system-variables.html#sysvar_flush

Suggested fix:
Add "only for MyISAM" into the reference.

[13 Apr 16:38] MySQL Verification Team

Hello tanaka-San,

Thank you for the report and feedback.

regards,
Umesh

[14 Apr 19:39] Edward Gilmore

Posted by developer:
 
Updated documentation as requested.
Thank you for the bug report.