PostgreSQL

PostgreSQL — MVCC relational server with the widest SQL surface and a deep extension ecosystem. PostgreSQL is a client/server relational database descended from Berkeley POSTGRES, governed by a contributor community rather than a company. Its extension mechanism is the reason it keeps absorbing adjacent categories: PostGIS made it a geospatial database, TimescaleDB a time-series one, and pgvector a vector store. The trade is operational weight — autovacuum, bloat and a process per connection are yours to manage. Founded 1996. Open source under PostgreSQL Licence.

We track it in 1 comparison — Database engines — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 4 other tools, and what follows is where it visibly separates from them.

Where it wins.

• ALTER TABLE — Minimal, the best figure of the 5 here.
• Extension ecosystem — 5, the best figure of the 5 here.
• Migration tooling — 5, the best figure of the 5 here.
• JSON support — Binary JSONB + indexes, the best figure of the 5 here.
• Managed options — Neon, Supabase, Amazon RDS, Amazon Aurora, Google Cloud SQL, Azure Database, PlanetScale, the best figure of the 5 here.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• Ops burden — 4, the weakest of the 5 here. SQLite records 1.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 25 of 26 tracked fields carry a value for PostgreSQL, and 20 of those cite a document you can open. Last verified 2026-07-01. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is DuckDB. PostgreSQL is ahead on Replication (Built-in async + synchronous against None) and PITR (Yes against No). DuckDB takes Ops burden (1 against 4) and Connection model (In-process (no connections) against Process per connection). That pattern repeats across the rest of the roster — see PostgreSQL alternatives for the other rivals, each compared the same way.

Founded

1996

Licence

PostgreSQL Licence (open source)

Fields we track

25 of 26

Last verified

2026-07-01

The strongest engine here on every axis except the one that costs you time. Nothing else combines transactional DDL, this much SQL and pgvector in the same box — and nothing else here needs you to understand autovacuum, bloat and connection pooling before the first incident.

Ops burden

45th of 5

Inferredverified 2026-07-01

ALTER TABLE

Minimal1st of 5

Vendor-claimedverified 2026-07-01source

Extension ecosystem

51st of 5

Vendor-claimedverified 2026-07-01source

Migration tooling

51st of 5

Inferredverified 2026-07-01

JSON support

Binary JSONB + indexes1st of 5

Vendor-claimedverified 2026-07-01source

Managed options

NeonSupabaseAmazon RDSAmazon Aurora+31st of 5

Inferredverified 2026-07-01

Replication

Built-in async + synchronous1st of 5

Vendor-claimedverified 2026-07-01source

PITR

●Yes1st of 5

Vendor-claimedverified 2026-07-01source

PostgreSQL is the right call in these situations, each one drawn from a field we actually record:

• Concurrent writers plus queries that outgrow simple key lookups.
• Anything storing embeddings, geometry or time series alongside rows.
• Teams who will run it managed, or who have someone who wants to own it.
• ALTER TABLE is your binding constraint. PostgreSQL records Minimal, the best figure in the Database engines roster. We define that field as how much of the schema you can change in place.
• Extension ecosystem is your binding constraint. PostgreSQL records 5, the best figure in the Database engines roster. We define that field as 1–5.
• Migration tooling is your binding constraint. PostgreSQL records 5, the best figure in the Database engines roster.
• JSON support is your binding constraint. PostgreSQL records Binary JSONB + indexes, the best figure in the Database engines roster.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• Ops burden. PostgreSQL records 4, the weakest of the 5 tools in the Database engines roster. SQLite records 1 on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 1 of the 26 fields we track for PostgreSQL are still blank: Max database size. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.