[MDEV-4251] problem with innodb and mariadb-10.0.1 Created: 2013-03-07 Updated: 2013-03-07 Resolved: 2013-03-07 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | roberto spadim | Assignee: | Sergei Golubchik |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
linux - mariadb binary file downloaded from mariadb website |
||
| Description |
|
hi guys, this option at mariadb 10.0.1 in my.cnf file: check the log file:
|
| Comments |
| Comment by Sergei Golubchik [ 2013-03-07 ] |
|
InnoDB is not mandatory (mandatory engines are impossible to disable, for example, there is no --skip-myisam option). But starting from MySQL-5.6 and MariaDB-10.0 InnoDB is the default storage engine. That's why the server refuses to start, it cannot resolve the name of the default storage engine. If you want to disable InnoDB, you need to change the default storage engine too, use the --option default-storage-engine=MyISAM |
| Comment by roberto spadim [ 2013-03-07 ] |
|
could it be automatic? |
| Comment by Sergei Golubchik [ 2013-03-07 ] |
|
it's a bit more complex. what if a user has explicitly specified --default-storage-engine=innodb ? in this case we should not automatically change it to myisam. So we'd need to track whether the value is default or it was specified by the user. Currently it's automatic in a sense that if innodb is compiled in - then innodb is a default. If innodb is not compiled in - then myisam is a default. |