Home / Companies / PlanetScale / Blog / Post Details
Content Deep Dive

What was the turning point for Postgres?

Blog post from PlanetScale

Post Details
Company
Date Published
Author
the spring of 1995 however, it had occurred to us that the Internet user community really needed an open source, SQL-based multiuser database.— Yu and Chen, in the foreword to PostgreSQL: Introduction and Concepts by Bruce MomjianIn 1996, Bruce Momjian fo
Word Count
2,273
Company Posts That Month
11
Language
English
Hacker News Points
-
Post removed?
No
Summary

Postgres became the leading default database for many new applications through a combination of technical adaptability, open governance, cloud distribution, and changing developer preferences rather than a single decisive event. Its origins in the 1980s emphasized extensibility and a permissive license, while a 1994–96 community revival transformed the abandoned research project into PostgreSQL and established its volunteer-led ownership model. The article identifies Heroku’s 2011 decision to make managed Postgres easy to provision as a particularly influential turning point, exposing many developers to the database and encouraging later services such as Amazon RDS to follow. Postgres then strengthened its position against document databases with JSONB support in 2014, benefited as uncertainty followed Oracle’s acquisition of MySQL, and overtook MySQL in Stack Overflow’s developer survey in 2023. By 2025–26, broad cloud availability, investment, pgvector support for AI applications, and frequent selection by coding agents had accelerated its adoption, although the article notes that MySQL remains important for large-scale workloads and that Postgres still faces challenges in horizontal sharding and extreme-scale performance.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
LLM 3 5,902 1,132 223 -2%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.