Bug #74748 Typo in error message: innodb_forced_recovery

• Submitted: 8 Nov 2014 15:16
• Modified: 1 Mar 2019 13:58
• Reporter: Daniël van Eeden (OCA)
• Status: Closed
• Category: MySQL Server: Errors
• Severity: S3 (Non-critical)
• Version: 5.7
• OS: Any
• CPU Architecture: Any
• Tags: error message, innodb

[8 Nov 2014 15:16] Daniël van Eeden

Description:
ER_INNODB_FORCED_RECOVERY
  eng "Operation not allowed when innodb_forced_recovery > 0."

It should be innodb_force_recovery instead of innodb_forced_recovery (without the d).

How to repeat:
Check message in sql/share/errmsg-utf8.txt against docs.

Suggested fix:
Update errmsg-utf8.txt

[8 Nov 2014 21:24] MySQL Verification Team

Thank you for the bug report.

[1 Mar 2019 13:58] Daniel Price

Posted by developer:
 
Typo. No changelog entry required.