40 Years of Postgres: Pages 11

A Postgres 8.x cylinder branches into Greenplum (2005) and, through ParAccel (2007), into Amazon Redshift (2012), both feeding one analytics dashboard; two separate three-node clusters are labeled CockroachDB 2015 and YugabyteDB 2017; a Neon 2022 Lakebase diagram shows Postgres compute above a cloud-storage lake with a sleeping elephant and a branching history labeled Main and Agent task.

The elephant rides a six-section rocket labeled AWS, GCP, Azure, Snowflake, Databricks, and Supabase, captioned 2013 onward; below, a DB-Engines popularity chart from 2013 to 2026 shows Oracle, MySQL, Microsoft SQL Server, and a rising orange Postgres line.

A growing family

Because the license permits it, Postgres code has been carried into Greenplum, ParAccel and the original Amazon Redshift engine. CockroachDB and YugabyteDB are relatives, speaking the Postgres language over different machinery. Neon (2022) separates compute from versioned storage so a database can branch and scale to zero.

Sources

Amazon Redshift and PostgreSQL (AWS documentation)
CockroachDB: PostgreSQL compatibility (docs)
YugabyteDB: why we reused the PostgreSQL query layer (2020)
Neon Serverless Postgres is Live (2022)
Neon architecture overview (docs)

Postgres keeps rising

Amazon RDS added Postgres in 2013 as its fourth engine; Google and Azure followed with managed services in 2018. In 2025 Snowflake acquired Crunchy Data and Databricks acquired Neon. On DB-Engines, Postgres has climbed steadily since 2013 and now sits fourth, close behind SQL Server.

Sources

Amazon RDS for PostgreSQL now available (AWS, 2013)
Cloud SQL for PostgreSQL generally available (Google Cloud, 2018)
DB-Engines ranking trend
Snowflake announces agreement to acquire Crunchy Data (2025)
Databricks agrees to acquire Neon (2025)

A growing family

Sources

Postgres keeps rising

Sources

Solutions & Platform

Resources

Change Management

Access & Security

AI & Agents

Comparisons

Company

Legal