The backup program should not backup INFORMATION_SCHEMA at all (it is mostly statistics that not stored persistently anyway, no need to backup/restore it, restore of it does not make sense)
>But for me it don't feel right that simply querying:
> SELECT * FROM information_schema.innodb_table_stats;
> can CRASH whole mariadb server (if innodb storage engine is disabled).
I agree it does not feel right, and needs to be fixed. By also take into account that disabling innodb is not something people do often, in contrary overwhelming majority runs innodb all the time.
If you would like to remove all trace of Innodb/XtraDB, and do not like to switch off all information schema plugins individually, use "ignore-builtin-innodb". The documentation of this variable here http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html is rather sparse, but it does disable all of innodb.
The backup program should not backup INFORMATION_SCHEMA at all (it is mostly statistics that not stored persistently anyway, no need to backup/restore it, restore of it does not make sense)
>But for me it don't feel right that simply querying: schema. innodb_ table_stats;
> SELECT * FROM information_
> can CRASH whole mariadb server (if innodb storage engine is disabled).
I agree it does not feel right, and needs to be fixed. By also take into account that disabling innodb is not something people do often, in contrary overwhelming majority runs innodb all the time.
If you would like to remove all trace of Innodb/XtraDB, and do not like to switch off all information schema plugins individually, use "ignore- builtin- innodb" . The documentation of this variable here http:// dev.mysql. com/doc/ refman/ 5.1/en/ innodb- parameters. html is rather sparse, but it does disable all of innodb.