PostgreSQL Was Renamed in 1996 to Reflect Its SQL Support

The database you know as PostgreSQL did not start with that name. For most of its early life it was simply called Postgres, a research project from the University of California at Berkeley led by Michael Stonebraker starting in 1986. Postgres was designed as an ambitious experiment in database management, and its early versions had their own query language rather than SQL. The modern name came only in 1996, when the project rebranded to PostgreSQL to reflect the fact that it had, by then, fully embraced SQL.

Understanding the rename requires understanding the origin. Berkeley's first database system, Ingres, had been a commercial success, and Stonebraker wanted to build on that. Postgres was intended to support sophisticated data types and a more relational model than its predecessor. The early design deliberately avoided SQL, using a query language called QUEL in the Ingres lineage and a PostQUEL variant in Postgres. That was a bold choice, but it put the project out of step with an industry that was racing toward SQL as the universal standard.

By the mid 1990s SQL had won. Databases that could not speak SQL were fighting a losing battle, and Postgres was no exception. In 1994 two Berkeley graduate students, Andrew Yu and Jolly Chen, added a SQL interpreter to the codebase and released the result as Postgres95. It was a crucial turning point. The following year the project was relicensed under a permissive license, and in 1996 the name was changed to PostgreSQL to make clear that this was a database that now spoke the industry standard language.

The rename was about honesty as much as marketing. Calling the software Postgres when its signature feature was broad SQL support would have been misleading. Developers evaluating databases in 1996 saw SQL compatibility as table stakes, and a name like PostgreSQL signaled that the system had caught up with the rest of the world. Over time people shortened it again to Postgres in everyday speech, but the official name carried the story of the project's evolution forward.

For a senior developer, the history matters because it explains a structural fact about the project. PostgreSQL is not a SQL database that added advanced features on top; it is a research database with ambitious data handling ideas that adopted SQL as its common language. That heritage is why PostgreSQL is so strong with complex queries, custom types, JSON support, and powerful indexing. The SQL is the foundation, but the engine underneath was built to be far more expressive than a bare relational store.

It is also a reminder that standards win. Postgres bet against SQL and lost the bet, and the project survived only by bending to the market. That willingness to adapt is exactly why PostgreSQL is still thriving decades later. Plenty of pioneering systems insisted on their own way and faded into history. PostgreSQL recognized the reality, changed course, and came out on top.

The next time you write a complex query against a PostgreSQL database, remember that you are using a system that had to change its name to keep pace with the industry. The name PostgreSQL marks the moment a research project decided to become the dependable, SQL speaking workhorse that millions of applications now rely on every day.