Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.5, 10.6, 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.7(EOL)
Description
Starting mysqld-install-db server setup with --enforce-storage-engine=InnoDB gives:
2021-08-16 11:45:47 23042769061632 [ERROR] InnoDB: Trying to create a MySQL system table `mysql`.`db` of type InnoDB. MySQL system tables must be of the MyISAM type!
|
ERROR: 1005 Can't create table `mysql`.`db` (errno: 168 "Unknown (generic) error from engine")
|
2021-08-16 11:45:47 23042925725632 [ERROR] Aborting
|
Interesting is also the 168 unknown error from InnoDB.
Perhaps a better way to handle this would be to automatically make system tables MyISAM (without any overwrite possibility). This would also make sense given that a server which already has MyISAM system tables can be started fine with --enforce-storage-engine=InnoDB thereafter, i.e. the "enforce" naming can be misleading in any case.
Another option is to disable the enforce-storage-engine option (or the InnoDB setting specifically) for mysqld-install-db only.
Attachments
Issue Links
- relates to
-
MDEV-6858 enforce_storage_engine option
- Closed
-
MDEV-30065 "mariadb-install-db --enforce-storage-engine=InnoDB" fails with InnoDB errors
- Stalled