As someone that admins hundreds of MySQL at work, I’d go with PostgreSQL.

The only reason I wouldn’t go with Postgres is if I planned to do other things on the same machine. MariaDB/MySQL has been around forever. You may find something that requires it — Wordpress¹, for example, requires MariaDB (or MySQL but use MariaDB) and doesn’t support Postgres.

Also, there’s solutions like Docker containers if you are running multiple things on the same server. But if you’re just learning and putting one thing on a Raspberry Pi as a project or whatever, you don’t need to learn Docker yet.

¹ I’m not recommending Wordpress. It’s ancient and has security issues all the time. But over 40% of sites on the Net still use it in some form. (I mean Wordpress.org, the open source project. The Wordpress company seems to be having some “crazy CEO” drama at the moment.)

We have both MySQL and PostgreSQL in our production environment. Postgres is way nicer as a user of the DB. I created a document months ago outlining a dozen different things that Postgres does that MySQL either doesn’t do or does worse. I can’t speak to managing the DB as I don’t have experience with that.

Another vote for Postgres, MySQL kind of blows.

Postgres, the extensions and open source community have been very helpful.

Postgis for images

CloudNative-pg for running DB clusters in kuberneties.

I’d vote for MariaDB or Postgres

Postgres is far superior in every way.

We used MySQL (and Percona XtraDB) servers at work, and it is so bad. So I made several presentations showing generic and specific reasons why Postgres is better. I had to cut a lot of content because MySQL is just that bad.

Some things may not seem relevant now, but as you keep the DB around long enough, you will appreciate the whole package of Postgres.

Things that will help a lot, but are extensions:

• pg_partman - for automatic partition management
• patroni - management of replicas, automatic failover - it does everything for you with simple commands

There is a DB comparison matrix, but hasn’t been updated in over a year, which is a shame, but still gives you the idea of how different databases support SQL features: link.

Spoiler: postgres has the most support, with a huge lead

Edit: MySQL is dead last, btw

Postgres is a more robust and better designed and developed product, also it’s not owned by fucking Oracle.

Postgres, hands down. It’s far better than MySQL in every way.

Postgres. It’s more strict by default, which leads to a lot fewer surprises.

Here’s my rule of thumb:

1. SQLite - if it’s enough
2. Postgres
3. MariaDB - if you don’t care about your data and just want the thing to work
4. MySQL - if you sold your soul to Oracle, but still can’t afford their license fee
5. Something else - you’re a hipster or have very unique requirements

I’d choose which ever one is not PostgreSQL.

My opinion is that of the two Postres is more “adult”. So if you want to"just wing it" MariaDB would work, but if you’re serious Postgres is a better choice. However Postgres also requires better understanding of you setup etc. So it’s a ROI game - what’s more important to your project, how complex your DB is, what are the requirements for availability, transaction security etc. There is no “better” or “worse” there’s “feasible” and “prohibitive” 😉

I have historically gone with PostgreSQL and had no complaints. The licensing issues concerning MySQL also give one pause (Oracle are greedy bastards who will use any excuse to extract money from captive customers, so depending on their properties is to be avoided). Having said that, these days, SQLite is probably sufficient for many workloads and has the advantage of not requiring a database server.

Avoid MySQL and MariaDB at all cost.

You aren’t exposing the database right?