Postgres vs MySQL in 2026: An Independent Decision Guide
Postgres is the default answer for new applications in 2026. MySQL is correct more often than the SERP admits. Here is the honest matrix, the ownership story, and the migration cost data nobody else publishes.
Quick decision matrix
| If you are building... | Pick |
|---|---|
| New web app, SaaS, complex queries | Postgres |
| Read-heavy CRUD, established LAMP / PHP stack | MySQL / MariaDB |
| Analytics with cloud lock-in tolerance | MySQL HeatWave or Postgres + Citus |
| Geospatial, GIS, time-series | Postgres + PostGIS / TimescaleDB |
| Massive scale, sharded OLTP, Vitess ecosystem | MySQL via Vitess |
See the honest MySQL case at /when-mysql-wins
Decision Tool
Workload
Scale
License tolerance
Select all three inputs to see verdict
The MySQL ownership timeline (1995-2024)
Oracle has owned MySQL since 2010. MariaDB is the open-governance fork.
The 2026 state of play
PostgreSQL 17 (September 2024)
Postgres has been the most admired database on the Stack Overflow Developer Survey since 2022. PostgreSQL 17 (September 2024 GA) adds logical replication failover, MERGE improvements, incremental backup, and planner advances. PostgreSQL 18 is in beta with a September 2026 release expected. The PostgreSQL Global Development Group governance means no single vendor controls the roadmap. Managed options: Neon, Supabase, Crunchy Bridge, RDS, Cloud SQL, Azure.
MySQL 8.4 LTS (April 2024)
MySQL 8.4 LTS ships with support until April 2032. Oracle also runs a 9.x innovation track. MySQL remains the dominant database in the LAMP ecosystem and powers WordPress (40%+ of the web), Shopify, Booking.com, and Slack via Vitess. Oracle's MySQL HeatWave is a proprietary cloud-only analytics accelerator available on OCI and AWS. MariaDB 11.x is the open fork with independent governance.
Production teams that made the call
Real engineering blogs, not vendor marketing. Full case studies at /case-studies.
Postgres in production
MySQL in production
Tools at a glance: 2026
Latest stable versions verified against postgresql.org and dev.mysql.com, April 2026.
| Database | Latest Stable (2026) | License | Owner / Governance | Best For |
|---|---|---|---|---|
| PostgreSQL | 17 (Sept 2024 GA), 18 beta | PostgreSQL License (BSD-style) | PostgreSQL Global Development Group | Default for new apps |
| MySQL | 8.4 LTS (Apr 2024) / 9.x innovation | GPLv2 + Oracle commercial | Oracle Corporation | LAMP / Vitess at scale |
| MariaDB | 11.x | GPLv2 | MariaDB Foundation + plc | MySQL compat, no Oracle |
| Percona Server | 8.4 (MySQL fork) | GPLv2 | Percona LLC | Drop-in MySQL + extras |
| MySQL HeatWave | 9.x + accelerator | Proprietary | Oracle Corporation | Oracle Cloud analytics |
Frequently asked questions
Is PostgreSQL better than MySQL?⌄
Depends on workload. Postgres wins for complex queries, JSONB, GIS, new applications, and teams that care about open governance. MySQL wins for read-heavy CRUD, established LAMP/PHP ecosystems, and sharded OLTP at massive scale via Vitess (YouTube, Slack, Booking.com). The honest matrix is on this page.
Is MySQL owned by Oracle?⌄
Yes. Oracle acquired Sun Microsystems in 2010, inheriting MySQL. The original MySQL founder (Monty Widenius) forked MariaDB in 2009-2010 in anticipation. PostgreSQL is governed by the PostgreSQL Global Development Group with no single corporate owner.
Should I migrate from MySQL to Postgres?⌄
Only if you have a clear pain trigger: Oracle ownership concern, specific feature blocker (PostGIS, JSONB indexing), or scale wall. Without one, the migration cost is rarely paid back. GitLab migrated over 2017-2020; they cited maintenance cost. Uber migrated the other way in 2016. See the migration cost page for real data.
Is MySQL still relevant in 2026?⌄
Yes. Booking.com, Shopify, Slack, YouTube run MySQL via Vitess. WordPress powers 40%+ of the web on MySQL. MariaDB is a healthy open fork. For LAMP stacks, established Vitess deployments, and MySQL DBA-heavy teams, MySQL is the right answer.
PostgreSQL vs MariaDB vs MySQL: which is best?⌄
PostgreSQL for new applications: best governance, richest features, no Oracle. MariaDB for MySQL compatibility without Oracle dependency: open governance, Wikipedia/Google use it. MySQL for existing Oracle-stack teams or Vitess at scale. Three valid choices for different situations.
Related engineering decisions
Polyglot teams choosing a database are often choosing a repo layout too.
DB client ergonomics differ by language. Language and DB decisions are linked.
Cache layer decision complements your primary DB choice.
DB choice is one node in the broader stack cost question.
Schema migrations drive CI cycles. Calculate the real cost.
DB choice locks in tech debt. Migrations surface it.