ArchLinux Decided to Move to MariaDB


Please shareShare on FacebookShare on Google+Tweet about this on TwitterShare on LinkedInShare on RedditDigg thisShare on StumbleUpon

What’s  MariaDB : is an community-developed fork of the MySQL relational database management system, the impetus being the community maintenance of its free status under the GNU GPL, as opposed to any uncertainty of MySQL license status under its current ownership by Oracle. The contributors are required to share their copyright with Monty Program AB.

The intent is also to maintain high fidelity with MySQL, ensuring a “drop-in” replacement capability with library binary equivalency and exacting matching with MySQL APIs and commands.It includes the XtraDB storage engine as a replacement for InnoDB, as well as a new storage engine, Aria, that intends to be both a transactional and non-transactional engine perhaps even included in future versions of MySQL.[7]

For years, MySQL has been fundamental to many server applications, especially those using the LAMP (Linux, Apache, MySQL, Perl/PHP/Python) software stack. Those days may be ending. BothFedora (Red Hat’s community Linux) and openSUSE (SUSE’s community Linux) will be switching out MySQL to MariaDB for their default database management system (DBMS) in their next releases.And finally     Archlinux  is  following  the   Opensource World.  :

Bellow is  Archlinux MalingList:


Because Oracle is Oracle is Oracle(…) I would like to propose migration to MariaDB. Jokes aside, the biggest problem with MySQL situation is that it becomes more and more closed source. Oracle stopped publishing regression tests, informative security advisories, they even hide bug reports and not include them in release notes. Very often their bzr repository is falling behind new releases.

On the other hand, MariaDB is truly open source (it doesn’t have enterprise-only options) and has open development model. Security advisories are published first on the mailing list for packagers with a patch for current release and information when the bug will be fixed and when the information about security hole can be published (Another advantage for ricers — some benchmarks show that MariaDB is faster.)

From packaging side, MariaDB is (still) drop-in replacement for MySQL. Unfortunately they are not fully compatible[4] and I don’t want to lie that I tested every package depending on MySQL before I pushed Maria to [community], but since April 2012 there has been no bug report about breakage. However I don’t want to use replaces=, because clearly it won’t work for everyone. Additionally switching now should be less problematic. MySQL 5.6 is already out and it is not as compatible with incoming MariaDB 10 as it was with 5.5 branch. While we keep Maria and MySQL branches in sync, it should be quite safe. To get back to the point… This is how I would see the migration plan: 1. Synchronize MariaDB and MySQL systemd units. 2. Move MariaDB to [extra]. 3. Rebuild packages depending on mysql/libmysqlclient/mysql-clients against its MariaDB counterparts. 4. Announce MySQL deprecation. 5. After month, drop MySQL to AUR.  

(Bartłomiej Piotrowski)



How to  move from  Mysql  to  MariaDB in Archlinux ?

Answer :

# systemctl stop mysqld 

# pacman -S mariadb libmariadbclient mariadb-clients 

# systemctl start mysqld 

# mysql_upgrade -p