| Bug #85045 | Warning of 'avoid_temporal_upgrade' incorrectly generated for skip-innodb option | ||
|---|---|---|---|
| Submitted: | 17 Feb 2017 9:45 | Modified: | 8 Mar 2017 18:19 |
| Reporter: | Daniel Blanchard | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Options | Severity: | S3 (Non-critical) |
| Version: | 5.7.17 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[8 Mar 2017 18:19]
Paul DuBois
Posted by developer: Noted in 8.0.1 changelog. If --skip-innodb or one of its variants was used, a spurious warning about avoid_temporal_upgrade was generated.
Description: There is a break statement missing after the case OPT_SKIP_INNODB code below in the function mysqld_get_one_option in mysqld.cc case OPT_SKIP_INNODB: sql_print_warning("The use of InnoDB is mandatory since MySQL 5.7. " "The former options like '--innodb=0/1/OFF/ON' or " "'--skip-innodb' are ignored."); case OPT_AVOID_TEMPORAL_UPGRADE: push_deprecated_warn_no_replacement(NULL, "avoid_temporal_upgrade"); break; Thus when the skip-innodb option is encountered, execution falls through to the following case. How to repeat: Start MySQL server with the --skip-innodb option (or one of its variants) and note the warning [Warning] The syntax 'avoid_temporal_upgrade' is deprecated and will be removed in a future release is incorrectly reported in the error log on startup. Suggested fix: Add the missing break statement