Am 27.11.2014 um 14:38 schrieb Casper Langemeijer:
i heard people tend to switch to mariaDB?any thoughts on that topic would be more than welcome ;-)We switched production databases (2000 db's 40G-10K, totaling 650G) for our internally developed software to MariaDB and have found a few small issues we didn't expect. Most of them stem from a bug with GROUP BY and joins <https://mariadb.atlassian.net/browse/MDEV-5719>. I doubt dbmail uses group by somewhere though. I'm very pleased with the quality of the MariaDB product and the openness of the development process.
i know only about one (fixed) MariaDB bug in context of DBMail
i guess we need some testers for 10.x as long MariaDB 10.x don't have major regressions or compatibility breaks besides new features all should work fineI'm running MariaDB 10.0.14 and will probably follow the new releases closely.
good to know, next year with Fedora 21 i have to switch to MariaDB 10 because keep the server at 5.5.x would be a dependency maintaince hell
http://fedoraproject.org/wiki/Changes/MariaDB10
I'm on dbmail 3.1.17 now and I get some segfaults now and then, but I doubt these are caused by MariaDB. I hope to find some time to dive into the issues soon, until that I've applied some duct tape and cronned /etc/init.d/dbmail start. Because I'm loadbalancing among a few servers, my users are not directly affected. And because there is no actual downtime, the issue is a relative low priority for me
they are likely still existing memory leaksonce in a while dbmail-imapd here explodes after allocated more the 1.5 GB RAM and i get a mail from the watchdog after restart - however - they are impossible MariaDB related, whatever the database layer does wrong (not said it does!) it must not lead in a segfault of the client application
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
