Databases

PostgreSQL vs MySQL

PostgreSQL has 5 supported release lines and MySQL has 2. PostgreSQL 14 reaches end of life on Nov 12, 2026, and MySQL 8.0 reached end of life on Apr 30, 2026. Both are open source: PostgreSQL under the PostgreSQL License, MySQL under GPL-2.0.

Last checked against endoflife.date and deps.dev.

Side by side

Every value links to its source. Where a row doesn’t apply to one of them, the cell says why.

Support and releases
PostgreSQLMySQL
Supported release lines

5 lines: 18, 17, 16, 15, 14

Next to end: 14 on Nov 12, 2026

endoflife.date

2 lines: 9.7 LTS, 8.4 LTS

Next to end: 8.4 on Apr 30, 2032

endoflife.date

Latest release

18.6

Released Aug 11, 2026

endoflife.date

9.7.2

Released Jul 28, 2026

endoflife.date

Releases in the last 12 months

No new release lines

Patch releases aren’t counted

endoflife.date

3 new release lines

Patch releases aren’t counted

endoflife.date

Security
PostgreSQLMySQL
Advisories published in the last 12 months

Not tracked as a package on OSV.dev

Security advisories

Not tracked as a package on OSV.dev

Security advisories

OpenSSF Scorecard

6.1 / 10

postgres/postgres, Aug 24, 2026

Scorecard

4.8 / 10

mysql/mysql-server, Aug 24, 2026

Scorecard

Licence and hosting
PostgreSQLMySQL
Licence

PostgreSQL License

Open source (permissive)

postgresql.org

GPL-2.0

Open source (copyleft)

That’s MySQL Community Server; Oracle also sells MySQL Enterprise Edition under a commercial licence.

github.com/mysql

How you run it

Self-hosted, or managed by most clouds (Amazon RDS, Google Cloud SQL, Azure) and platforms such as Supabase and Neon

Self-hosted, or managed by most clouds (Amazon RDS, Google Cloud SQL, Azure)

Adoption
PostgreSQLMySQL
GitHub stars

22.4K

postgres/postgres

GitHub

12.5K

mysql/mysql-server

GitHub

Which fits your constraints

Read across for what matters to you. Each answer comes from the data above or the project’s licence and hosting options.

How PostgreSQL and MySQL fit common constraints
PostgreSQLMySQL
An open-source licence

Yes: PostgreSQL License

Yes: GPL-2.0

Someone else runs it for you

Yes: From Amazon RDS, Google Cloud SQL, Azure, Supabase, Neon

Yes: From Amazon RDS, Google Cloud SQL, Azure

You can run it on your own servers

Yes: Yes, it’s software you install

Yes: Yes, it’s software you install

A long support window

18 is supported until Nov 14, 2030

9.7 LTS is supported until Apr 30, 2034

What each is good at

PostgreSQL

Advanced open-source relational database with rich features

Strengths

  • ACID compliant with strong data integrity
  • Advanced features (JSON, full-text search, GIS)
  • Extensible with custom functions and types
  • Excellent performance for complex queries
  • Strong community and ecosystem

Trade-offs

  • Steeper learning curve than MySQL
  • Slightly slower for simple read-heavy workloads
  • More memory intensive

Common uses

  • Transactional applications
  • Data warehousing
  • GIS applications
  • JSON document storage

MySQL

Popular open-source relational database optimized for web applications

Strengths

  • Widely adopted with extensive documentation
  • Fast for read-heavy workloads
  • Easy to set up and use
  • Large ecosystem of tools and hosting options

Trade-offs

  • Less advanced features than PostgreSQL
  • Some storage engines lack full ACID compliance
  • Limited support for complex data types

Common uses

  • Web applications
  • Content management systems
  • E-commerce platforms

From StackPrism’s curated notes. Pricing isn’t covered here: it changes often, so check each vendor’s pricing page.

When teams weigh these two

Two open-source relational databases that every major cloud offers as a managed service, so availability rarely decides it. Teams usually weigh PostgreSQL’s extensions (PostGIS, pgvector) and richer types such as JSONB against MySQL’s long history in LAMP-style web stacks.

How this comparison works

Release lines and end-of-life dates come from endoflife.date, release counts from deps.dev’s publish dates, and advisories from OSV.dev, counted once per flaw even when it’s listed under several ids, and checked against CISA’s list of vulnerabilities known to be exploited. Status and incident history come from each vendor’s public status feed; licences from each project’s licence file or the vendor’s licensing page, linked in the table.

The data refreshes every few hours and the time it was checked is shown above. There’s no pricing and no overall winner: which one fits depends on your constraints. To see how the versions you actually run hold up, check your repo.

Already using one of them?

Paste a public GitHub repo and see what’s vulnerable, end of life or deprecated in it today. Free, no sign-up.