Every few months someone posts "MySQL or PostgreSQL?" and the comments turn into a religion war within minutes. I have run both in production — MySQL behind WordPress sites and a legacy CRM, PostgreSQL behind Nextcloud, a couple of Django apps, and most of what I build today. This is the comparison I wish someone had given me before I picked sides: no benchmarks with suspicious methodology, just what actually differs when you live with these databases.
The one-paragraph answer
If you are starting something new in 2026, pick PostgreSQL unless you have a specific reason not to. If you are running WordPress or an older PHP app, stay on MySQL/MariaDB because that is what the ecosystem expects and there is no prize for swimming upstream. The interesting part is why.
Where PostgreSQL genuinely wins
Data types and correctness. PostgreSQL has jsonb with real indexing, arrays, ranges, proper UUID types, and constraints that actually constrain. MySQL spent years silently ignoring things like CHECK constraints, and while modern MySQL has improved a lot, the mindset difference remains: PostgreSQL assumes your data matters and refuses to guess. MySQL historically preferred to coerce your value into something that fits. I have debugged data corruption from silent truncation on MySQL. I have never had PostgreSQL silently mangle a value.
Complex queries. Window functions, CTEs, lateral joins, full-text search that does not require a plugin — PostgreSQL treats these as everyday tools. The first time you replace three nested application loops with one WITH RECURSIVE query, you understand why people get evangelical about it.
The planner and tooling. EXPLAIN (ANALYZE, BUFFERS) in PostgreSQL is the best query-debugging tool I have used anywhere, commercial databases included. When something is slow, PostgreSQL tells you the truth in detail. MySQL's EXPLAIN has gotten better, but it still feels like reading tea leaves by comparison.
Extensions. PostGIS for geospatial, pg_stat_statements for performance, pg_trgm for fuzzy search. The extension ecosystem lets PostgreSQL grow into workloads instead of forcing you to add another database to your stack.
Where MySQL genuinely wins
The ecosystem you are already in. WordPress, most shared hosting, cPanel, half the PHP tutorials on the internet — they assume MySQL or MariaDB. Fighting that is wasted effort. When I set up WordPress for someone, I use MariaDB and never think about it again.
Operational simplicity at small scale. MySQL has a reputation, partly earned, for being easy to run acceptably with little tuning. PostgreSQL is not hard, but it rewards understanding things like vacuuming and connection limits sooner. On a tiny VPS running one blog, you will notice MySQL's "just works" quality more than any planner sophistication.
Some managed and replication scenarios. MySQL's replication story is mature and well understood, and lots of managed offerings are built around it. This matters less every year, but in some organizations the MySQL runbooks and the people who know them are already there.
The honest middle ground
For typical CRUD applications — a blog, a small SaaS, an internal tool — both databases are so far past "good enough" that the choice barely matters. Your queries will be simple, your data will be small, and either engine will be bored. The performance differences people argue about on benchmarks show up at scales most of us will never reach.
What actually determines your experience:
- Which one your framework supports best (Django and Rails are PostgreSQL-first; WordPress is MySQL-only)
- Which one your team already knows how to back up and restore
- Whether you will need PostgreSQL-specific features later (JSONB queries, full-text search, GIS)
What I actually do
New project, my choice: PostgreSQL, every time. Nextcloud's own documentation recommends it, Django loves it, and the day I need a feature like jsonb indexing or a window function, it is already there. I have migrated apps off MySQL; I have never once wished to migrate back.
WordPress or a client's existing PHP stack: MariaDB, no drama, no migration heroics.
If you are learning databases for the first time: learn PostgreSQL. The habits it teaches — constraints, transactions, reading query plans — transfer everywhere. The habits MySQL sometimes teaches (hoping the engine coerces things the way you meant) do not.
And whichever you pick: set up the backups, test the restore, and turn on slow query logging. That decision affects your Sunday mornings far more than the logo on the database ever will.
Top comments (0)