PostgreSQL became the world's default relational database without anyone noticing, and that is exactly the point. No launch event, no killer-feature moment, no dramatic overthrow of a rival. It simply kept showing up — in surveys, on cloud dashboards, in the default of every new project's README — until one day it was the table everyone sits at and no one remembers setting it.
The quiet part starts with its origins. Postgres began as POSTGRES at UC Berkeley, a research offshoot led by Michael Stonebraker as a follow-up to his earlier Ingres project — a line of work born in the academic world, not the market. Implementation started in 1986. For its first decade it was a university project, interesting to a few thousand people and essentially unknown to everyone else. The rename to PostgreSQL came in 1996, to reflect the new SQL support, with version numbers reset to carry on from 6.0. The first 6.0 release shipped on January 29, 1997.
From there, the growth was pure accumulation. A new major version roughly every year, per the project's versioning policy. Steady, unglamorous feature additions for two decades. Nothing about any single release was destined to change the world; the compounding of all of them did.
The proof shows up in the polls. In the Stack Overflow Developer Survey, Postgres spent years chasing MySQL: usage sat at 33% versus MySQL's 59% in 2018. By 2024 it had passed it, reaching 49% and claiming most-popular for a second straight year. The 2025 survey found it the most used database, the most admired (a fourth consecutive title), and the most wanted for a fifth year running. DB-Engines ranks it among the top systems globally, the leading open-source option, and made it its 2023 DBMS of the Year. All that, without a single headline moment.
It helps that adoption is now painless. An extension ecosystem has grown up around the core, and every major cloud platform offers a managed Postgres — fire it up and it just runs. There is no over-claiming here: Postgres does not do everything. MySQL and SQLite still hold real territory, and the clouds' proprietary Postgres-compatible offerings signal the same appetite. But across all of it, a common thread is visible — most new projects reach for Postgres by default, simply because it works.
The cadence continues: PostgreSQL 18 shipped on September 25, 2025, keeping the annual pace, so the trend shows no sign of stopping. The default was not decreed. It was accumulated, release by release, extension by extension, survey by survey, until it felt like gravity.
That is the real story worth telling. The world's default database did not win a competition. It just kept being useful, one quiet release at a time.