You're right, but as... http://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html
_"innodb_file_per_table is enabled by default in MySQL 5.6.6 and higher. You may consider disabling it if backward compatibility with MySQL 5.5 or 5.1"_ _---_ Andrea Brancatelli Schema31 S.p.a. Responsabile IT ROMA - BO - FI - PA ITALY Tel: +39. 06.98.358.472 Cell: +39 331.2488468 Fax: +39. 055.71.880.466 Società del Gruppo SC31 ITALIA Il 2016-02-23 10:48 Reindl Harald ha scritto: > Am 23.02.2016 um 10:40 schrieb Andrea Brancatelli: > >> Probably you should do an optimize table on dbmail_messages and such. >> >> Consider it will take quite long time, and, even if it's not blocking, >> it will slow down the mysql server pretty much. >> >> Furthermore take in consideration that on "first" run of dbmail-util the >> mail il flagged for deletion and on the subsequent run is actually deleted. >> >> In general it's pretty normal to have some spurious datas in the DB. >> >> Last consideration, if you're very concerned about disk space take in >> consideration enabling InnoDB Barracuda and do an ALTER TABLE >> Engine=InnoDB ROW_FORMAT=COMPRESSED; on the bigger tables - they will >> shrink down a lot > > both only works with non-default "innodb_file_per_table = 1" setting, > otherwise all data is in the global table space > > _______________________________________________ > DBmail mailing list > DBmail@dbmail.org > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
