Suggestions  - 
Which would you suggest... MySQL or MariaDB and why?
(explain below)

Reason I'm asking. I'm about to write a followup to the "My.cnf tuning – Avoid this common pitfall" article I posted last year and I would like to cover some of the differences, pros and cons between MariaDB and MySQL. Curious of the split.
754 votes  -  votes visible to Public
Other (explain why below)
Matjaž Mozetič's profile photoIron Bug's profile photodrak nibe's profile photoAlexey Parshin's profile photo
Uwe Seher
PostgreSQL. Because it is better.
Rafi X
For small projects - MariaDB.
When I think about Oracle I see asterisk.
I read that bugs are issued faster than in MySQL.
But for more advanced DBases you use Postgres or something better.
MySQL and MariaDB are basically the same. MySQL was acquired by Oracle. Oracle isn't the best with free software (some exceptions exist). Most MySQL devs created and moved to MariaDB to ensure its future.

If you must choose between those two, I'd suggest MariaDB.
Unless you desperately need paid professional Support from Oracle, use MariaDB
MariaDB also has paid support with the enterprise versions. Have been
using that, they are very helpful.
Surely the answer completely depends on what you're using the DB for?! 
PostgreSQL it's just as free, has better support (by which I mean it's easier to buy the time of real PostgreSQL experts), and has features like an enterprise license from Oracle or MS.
I would say PostgreSQL too. When it comes to geographic data, PostgreSQL is the best.
PostgreSQL! For starters because your db files don't grow incessantly until you clean up.
PostgreSQL. More robust and more capable SQL implementation.
I ran multiple live Mariadb's with +-600 Gb of data and master slave replication. It never missed a heartbeat. Backups was a pain though.
Go for mysql, it is already the most popular open source database in the world, it has good support from Oracle and all major Linux vendors (RedHat, Ubuntu). It also comes with more features in enterprise edition.
People who advocate noSQL as a replacement for SQL clearly understand neither. SQL and noSQL are different (in particular, noSQL is many things), and each excel at solving certain problems. Use the right tool for the job: sometimes it's noSQL, sometimes it's SQL.
+Dave Voorhis
people that ask dummy questions like "what db is the best ever" deserve the same meaningless answers.
MySQL was design for people with small projects and small databases. It is nearly ideal for such situations.
For large projects, databases, heavy SELECTs, complicated stored procedures - there is PostgreSQL.
Using MySQL or MariaDB in that case is possible, but painful.
Also, two MySQL forks are drifting apart as we speak.
Add a comment...