Page 1 of 1

Is it safe to change mailscanner database from MyISAM to InnoDB

Posted: 22 Jun 2024, 17:45
by nermin_dadan
Hello,
recently I used mysqltuner.pl to optimize MariaDB on my server.

Is it safe to change mailscanner database from MyISAM to InnoDB?

-------- MyISAM Metrics ----------------------------------------------------------------------------
[!!] Consider migrating 13 following tables to InnoDB:
[--] * InnoDB migration request for mailscanner.mcp_rules Table: ALTER TABLE mailscanner.mcp_rules ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.users Table: ALTER TABLE mailscanner.users ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.whitelist Table: ALTER TABLE mailscanner.whitelist ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.mtalog Table: ALTER TABLE mailscanner.mtalog ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.user_filters Table: ALTER TABLE mailscanner.user_filters ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.sa_rules Table: ALTER TABLE mailscanner.sa_rules ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.audit_log Table: ALTER TABLE mailscanner.audit_log ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.maillog Table: ALTER TABLE mailscanner.maillog ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.inq Table: ALTER TABLE mailscanner.inq ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.outq Table: ALTER TABLE mailscanner.outq ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.blacklist Table: ALTER TABLE mailscanner.blacklist ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.geoip_country Table: ALTER TABLE mailscanner.geoip_country ENGINE=InnoDB;
[--] * InnoDB migration request for mailscanner.saved_filters Table: ALTER TABLE mailscanner.saved_filters ENGINE=InnoDB;

Thanks!