PostgreSQL

PostgreSQL is an open-source object-relational database management system whose development began at the University of California, Berkeley in 1986 under the POSTGRES project led by computer scientist Michael Stonebraker. It was created as a successor to the earlier Ingres system and was intended to explore database models and capabilities that went beyond the assumptions of conventional relational database products. The project’s research orientation contributed features such as extensibility, user-defined types, procedural languages, and support for complex data relationships. The system was initially known as POSTGRES. After the project added SQL support in the mid-1990s, it was renamed PostgreSQL in 1996 to reflect the combination of its POSTGRES architecture and SQL capabilities. The database was released under the liberal PostgreSQL License, which allows commercial and non-commercial use, modification, and redistribution. This licensing model helped PostgreSQL become both an independent community project and a foundation for commercial database services, hosted cloud offerings, enterprise distributions, and application platforms. PostgreSQL is commonly described as an object-relational database because it combines relational tables, transactions, constraints, indexes, and SQL with extensibility mechanisms and support for richer data types. It supports features including multi-version concurrency control, write-ahead logging, foreign keys, common table expressions, window functions, partitioning, replication-related technologies, full-text search, JSON and JSONB data, geographic and custom data types, and user-defined functions. The core server can be extended through procedural languages, extensions, operators, access methods, and custom types. These capabilities have made it useful for transactional systems, analytical workloads, geospatial applications, content management, finance, software-as-a-service platforms, and general-purpose application development. Unlike a database product controlled by a single commercial corporation, PostgreSQL is developed through an open, merit-based community process. The PostgreSQL Global Development Group coordinates releases and maintains the project, while contributors from universities, independent communities, consulting firms, cloud providers, software vendors, and end-user organizations work on the code, documentation, testing, translations, and infrastructure. Companies may provide commercial support or package PostgreSQL into proprietary services, but no single company owns the PostgreSQL project in the conventional corporate sense. The project has maintained a regular major-release cycle, with each major version introducing new capabilities while preserving a strong emphasis on standards compliance, reliability, backward compatibility, and data integrity. Minor releases address bugs and security issues. PostgreSQL is distributed for major operating systems and is available through Linux distributions, package managers, container ecosystems, and cloud database services. Its ecosystem includes administration tools, drivers, extensions, backup utilities, monitoring products, and managed offerings from multiple providers. PostgreSQL’s brand positioning centers on technical depth, openness, extensibility, standards-oriented engineering, and dependable data management rather than on a proprietary vendor identity. It competes and is often compared with commercial relational databases such as Oracle Database and Microsoft SQL Server, as well as other open-source systems such as MySQL and MariaDB. PostgreSQL remains an active international project and is widely used directly by organizations and indirectly through hosted database platforms and software products built on top of it.

PostgreSQL traces its history to the POSTGRES database project at the University of California, Berkeley. The project began in 1986 under the direction of Michael Stonebraker, following his earlier work on the Ingres database system. POSTGRES was designed as a research platform for exploring database technologies that could represent more complex application data and could be extended by users and developers. Its architecture introduced ideas that later became important to PostgreSQL, including extensible data types, user-defined functions, inheritance-related capabilities, and a system designed to accommodate new database mechanisms rather than limiting the server to a fixed set of built-in types. The Berkeley research project produced several releases and influenced academic and commercial database development. In 1994, Andrew Yu and Jolly Chen added an SQL language interpreter to the system. This transition was significant because it made the database more accessible to the wider software community while retaining the extensibility inherited from POSTGRES. The project was renamed PostgreSQL in 1996, signaling its support for SQL as well as its POSTGRES foundations. The name is commonly shortened to Postgres. After the original Berkeley project ended, development continued through an international open-source community. PostgreSQL adopted a permissive license that permits use, modification, and redistribution without the copyleft obligations associated with some other open-source licenses. The project’s governance consequently developed around contributors and a release process rather than around a conventional corporate owner. The PostgreSQL Global Development Group became the public identity associated with coordinating releases, documentation, infrastructure, and community processes. During the late 1990s and 2000s, PostgreSQL evolved from a research-derived database into a general-purpose production system. Major work included improvements to transaction processing, multi-version concurrency control, indexing, query planning, write-ahead logging, replication, standards support, procedural languages, and administration. The project also developed a substantial extension ecosystem. Extensions allow functionality such as geographic data processing, additional indexing methods, monitoring, and specialized data types to be added without placing every capability in the core server. The release series was renamed and standardized over time. PostgreSQL 7.0, released in 2000, marked an important stage in the project’s maturation and included improved support for foreign keys and related relational features. PostgreSQL 8.0, released in 2005, introduced a native Windows version and other substantial improvements. PostgreSQL 9.0, released in 2010, added built-in streaming replication and hot standby capabilities, strengthening its suitability for high-availability and read-scaling architectures. PostgreSQL 9.2, released in 2012, expanded support for JSON and introduced broader performance and replication improvements. PostgreSQL 9.4, released in 2014, added JSONB and logical decoding, both of which helped broaden its use in modern application workloads. The project later moved to a single-number major-version convention. PostgreSQL 10, released in 2017, introduced declarative table partitioning, logical replication, and a revised versioning scheme. PostgreSQL 11 and subsequent releases continued development in partitioning, parallel query execution, just-in-time compilation, stored procedures, monitoring, query planning, replication, and operational tooling. PostgreSQL 12 through 15 added further performance, indexing, security, and administration improvements, while also strengthening support for JSON, partitioned tables, and large-scale workloads. PostgreSQL 16 was released in 2023, followed by PostgreSQL 17 in 2024. Recent releases have continued the project’s pattern of incremental improvements to query execution, vacuuming, replication, observability, SQL features, and developer ergonomics. The project maintains separate major versions for a defined support period and publishes minor releases containing bug fixes and security corrections. Today, PostgreSQL is used in self-managed infrastructure, enterprise applications, public-sector systems, research, software-as-a-service products, and managed database services. Its ecosystem includes official client libraries and drivers, administration tools, cloud platforms, consulting firms, training providers, and thousands of extensions and integrations. PostgreSQL remains independent of any single commercial vendor, although many technology companies contribute code, sponsor developers, offer commercial support, or provide hosted PostgreSQL-compatible services.

1. 2024PostgreSQL 17 released

   The release added improvements in vacuuming, write-ahead logging, replication, JSON processing, query execution, and administration.

   Source
2. 2023PostgreSQL 16 released

   The release improved parallel query execution, logical replication, monitoring, SQL functionality, and general performance.

   Source
3. 2017PostgreSQL 10 adopts the modern versioning scheme

   PostgreSQL 10 introduced the project’s current single-number major-version convention and added declarative partitioning and logical replication.

   Source
4. 2014PostgreSQL 9.4 introduces JSONB

   Version 9.4 added JSONB and logical decoding, strengthening PostgreSQL’s role in applications using semi-structured data.

   Source
5. 2010Streaming replication and hot standby arrive

   PostgreSQL 9.0 added built-in streaming replication and hot standby features for higher availability and read-oriented architectures.

   Source
6. 2005PostgreSQL 8.0 released

   Version 8.0 included a native Windows release and continued major work on enterprise database capabilities.

   Source
7. 2000PostgreSQL 7.0 released

   The 7.0 release represented an important step in the project’s development as a production-oriented relational database.

   Source
8. 1996The project is renamed PostgreSQL

   The name PostgreSQL was adopted to reflect the system’s SQL support and its POSTGRES heritage.

   Source
9. 1994SQL support is added

   Andrew Yu and Jolly Chen added an SQL language interpreter, broadening the project beyond its earlier research-oriented interface.

   Source
10. 1986POSTGRES project begins at Berkeley

    Michael Stonebraker began the POSTGRES database research project at the University of California, Berkeley.

    Source

An open, extensible, standards-oriented, and reliability-focused alternative to proprietary relational database systems, with a broad ecosystem spanning self-hosted deployments, commercial support, and managed cloud services.

• PostgreSQL database serverDatabase management system1996

  The core PostgreSQL server provides relational and object-relational database capabilities, including SQL processing, transactions, concurrency control, constraints, indexes, recovery, security controls, procedural languages, and extensibility. It is distributed as open-source software for major operating systems and can be deployed on physical servers, virtual machines, containers, and cloud infrastructure.

• PL/pgSQLDatabase programming language

  PL/pgSQL is PostgreSQL’s built-in procedural language for writing functions, procedures, triggers, and server-side logic. It enables developers to combine SQL with variables, control flow, exception handling, and other programming constructs close to the data, while PostgreSQL also supports additional procedural languages through its extensible architecture.

• PostgreSQL extensionsDatabase extension ecosystem

  Extensions allow PostgreSQL installations to add data types, functions, operators, index methods, foreign-data wrappers, and other capabilities. The ecosystem includes official and community extensions for geographic information, advanced indexing, monitoring, time-series workloads, authentication, and specialized application requirements. Extensions are a central part of PostgreSQL’s positioning as an adaptable database platform.

• 2017Move to single-number major versionsStrategy

  The project revised its version-numbering policy to make major releases and support expectations easier to communicate.

  What changed. Beginning with PostgreSQL 10, major releases used a single integer, with minor releases using a second number.

  Aftermath. Later major releases followed the single-number convention, including PostgreSQL 11 through PostgreSQL 17.

  Source
• 1996Adoption of the PostgreSQL nameStrategy

  The project had added SQL support while retaining the architecture and identity of POSTGRES. A new name was needed to communicate both elements.

  What changed. The community adopted PostgreSQL, combining the project’s POSTGRES heritage with its SQL capabilities.

  Aftermath. The name became the enduring identity of the open-source database project, while Postgres remained a widely used informal short form.

  Source

• 2024PostgreSQL 17 released

  The project announced PostgreSQL 17 with enhancements to vacuuming, write-ahead logging, query execution, replication, JSON processing, and operational administration.

  Product launchProduct generation
  Source
• 2023PostgreSQL 16 released

  The PostgreSQL project released version 16, adding improvements across query parallelism, logical replication, monitoring, performance, and SQL functionality.

  Product launchProduct generation
  Source

1. PostgreSQL History
2. PostgreSQL About Page
3. PostgreSQL Documentation
4. PostgreSQL 16 Released
5. PostgreSQL 17 Released
6. PostgreSQL Wikipedia Article
7. PostgreSQL 7.0 released
8. Streaming replication and hot standby arrive
9. PostgreSQL 9.4 introduces JSONB
10. PostgreSQL 10 adopts the modern versioning scheme