Details
Major
Description
debian/additions/my.cnf file turns on log-bin by default:
log_bin = /var/log/mysql/mariadb-bin log_bin_index = /var/log/mysql/mariadb-bin.index
Unless it was done on purpose, it's not a great idea because
a) it obviously affects performance for those who doesn't need the binlog;
b) it causes unpleasant side-effects, due to statement logging being unsafe for various configurations and statements (warnings in the error log, errors on using InnoDB + READ-COMMITTED);
c) it's different from MySQL setup.
If it's possible to do it carefully now (without overriding custom cnf files on upgrade), it would be good to fix it in 5.5. In 10.0 it should be safe enough to fix, since it's only alpha.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I've discussed this with Krisitan (who has way more apt-get experience than I do).
And we agreed not to fix it, at least, not in 5.5.28.
You're right, it would've been better to have binlog disabled from the start. But as we have it enabled, it's safer to keep it this way. Users might let the new my.cnf to overwrite the old one on upgrade (and there are users, who do that!), which would cause binlog to be disabled after the upgrade, breaking the replication.