PostgreSQL is a very strong open source ORDBMS (object-relational database relational system) that has a history of over twenty years. The BSD permits PostgreSQL to be distributed as an open source allowing developers and related companies around the world to participate.

Unlike other relational database systems, PostgreSQL allows users to create unique operators, complex data types, aggregate functions, data type conversion character, and other various database objects through the SQL function.
Based on these characteristics, PostgreSQL functions exceed a simple data store. The user can easily implement limitless functions, almost like a new programming language, depending on the creativity of the developers.
History of PostgreSQL
1982 – Ingres project
PostgreSQL grew from the Ingres project, which started at the University of California Berkeley. Michael Stonebraker, Ingres project leader, left UC Berkeley to commercialize the use of Ingres in 1982. He returned to school in 1985 and realized that there was a growing pattern of problems in the database system in the early 1980s. He set out to create solutions to the escalating problems. Post-Ingres, the project following Ingres was separated except for a portion of the code.
1988 – Post-Ingres
Post-Ingres introduced a prototype version at the 1988 ACM SIGMOD conference. The post-Ingres project team launched the first version in 1989, the second version in 1990 and the third version in 1991. The project came to an end on June 30, 1994 after the 4.2 version was released. The open source developers were able to announce POSTGRES, through the BSD (Berkeley Software Distribution) license.
1994 – Postgres95
UC Berkeley graduates Andrew Yu and Jolly Chen added an interpretation to the Ingres based query system and created “Postgres95”. Andrew and Jolly replaced the console application, Monitor to PSQL, and released the source code to the web.
1996 – PostgreSQL
In 1996 “Postgres95” was renamed. “Postgres95” was renamed because it included the year and would no longer be relevant. The new name, PostgreSQL, was created to represent the synthesis of POSTGRES and the newly added SQL function. The previous version 4.2 that was created at Berkeley for the POSTGRES project was labeled as version 5.0 and the following was named version 6.0.
Common questions
Is PostgreSQL free to use?
Yes. PostgreSQL is released under a permissive open-source license and has no licensing fees for self-hosting. Managed versions from cloud providers are billed separately for compute, storage, and related services.
What is the difference between the relation cache and the system catalogs?
The system catalogs, such as pg_class and pg_attribute, are the on-disk source of truth for table and index metadata. The relation cache is each backend process's in-memory, parsed copy of that metadata, kept to avoid repeated catalog lookups during query planning and execution.
Can PostgreSQL handle graph-style queries?
PostgreSQL itself is relational, but extensions such as Apache AGE add graph query support on top of standard PostgreSQL storage, and recursive common table expressions can handle many graph traversal patterns without any extension at all.
Why does a schema change sometimes slow down other queries?
Altering a table's structure invalidates the cached relation descriptors held by every other backend process, and acquiring the lock needed for the change can briefly block concurrent statements against that table. Running such changes during low-traffic periods reduces the impact.
Should I write 'id = 5' or 'id = 5::int' in a query?
For a plain integer literal compared to an integer column, PostgreSQL infers the type correctly without a cast. Explicit casts become useful when the literal is ambiguous, such as a quoted string being compared against a non-text column.
Sources
About this page
Last reviewed October 30, 2026 by the Nine Bits editors. Read our editorial policy or report an error.