Training Example: PostgreSQL Global Development Group – Review the Data, Give Your Score & Compare to the Real AI Evaluation

[IMG: PostgreSQL Elephant Logo]

[H2] New to PostgreSQL?

PostgreSQL is a powerful, open source object-relational database system with over 35 years of active development
that has earned it a strong reputation for reliability, feature robustness, and performance.

There is a wealth of information to be found describing how to install and use PostgreSQL through the official documentation.
The open source community
provides many helpful places to become familiar with PostgreSQL,
discover how it works, and find career opportunities. Learn more on
how to engage with the community.

Learn More
Feature Matrix
Governance

[H2] Latest Releases

2026-06-04 -
PostgreSQL 19 Beta 1 Released!

The PostgreSQL Global Development Group announces that the first
beta release of PostgreSQL 19 is now
available for download. This release contains
PostgreSQL 19 feature previews ahead of general availability, though
some details of the release can change during the beta period.

You can find information about all of the PostgreSQL 19 features and
changes in the release notes.

In the spirit of the open source PostgreSQL community, we strongly
encourage you to test the new features of PostgreSQL 19 on your
systems to help us eliminate bugs and other issues. While we do not
advise you to run beta versions in production environments, we
encourage you to find ways to run your typical application workloads
against this beta release.

Your testing and feedback help the community ensure that PostgreSQL 19
upholds our standards of delivering a stable, reliable release of the
world's most advanced open source relational database. Please read more about
our beta testing process
and how you can contribute.

PostgreSQL 14 will stop receiving fixes on November 12, 2026. If you
are running PostgreSQL 14 in a production environment, we suggest that
you make plans to upgrade to a newer, supported version of PostgreSQL.
Please see our versioning policy
for more information.

18.4 · 2026-05-14 · Notes
17.10 · 2026-05-14 · Notes
16.14 · 2026-05-14 · Notes
15.18 · 2026-05-14 · Notes
14.23 · 2026-05-14 · Notes

Download
Why Upgrade?
Security

[H2] Upcoming Events

2026-06-16 – 2026-06-18 · POSETTE: An Event for Postgres 2026

[IMG: PostgreSQL Community Event]

2026-06-25 – 2026-06-26 · Swiss PGDay 2026

[IMG: PostgreSQL Community Event]

2026-09-08 · PGDay UK 2026

[IMG: PostgreSQL Community Event]

2026-10-20 – 2026-10-23 · PGConf.EU 2026

[IMG: PostgreSQL Community Event]

2026-10-25 · PGDay Israel 2026

[IMG: PostgreSQL Community Event]

2026-10-30 · PG Down Under 2026

[IMG: PostgreSQL Community Event]

2026-11-18 – 2026-11-21 · PgConf.Nepal 2026

[IMG: PostgreSQL Community Event]
indicates that an event is recognised under the community event guidelines and is directly helping the PostgreSQL community.

Check Schedule
Add Your Event

[H2] Mailing Lists

The PostgreSQL mailing lists enable you to interact with active community participants on subjects related to the development of PostgreSQL, discovering how to use PostgreSQL, or learning about upcoming events and product releases.

In order to manage your mailing list subscription, you need a PostgreSQL community account. Signing up is easy and gives you direct access to the global PostgreSQL community.

Subscribe
View Archives

[H2] Quick Links

Downloads

Packages
Source

Software Catalogue

File Browser

[H1] Downloads
[H2] PostgreSQL Downloads
PostgreSQL is available for download as ready-to-use packages or installers for
various platforms, as well as a source code archive if you want to build it
yourself.
[H3] Packages and Installers
Select your operating system family:
Linux
[IMG: Linux Logo]
macOS
[IMG: Apple Logo]
Windows
[IMG: Windows Logo]
BSD
[IMG: BSD Logo]
Solaris
[IMG: Solaris Logo]
Select your Linux distribution:
Debian
[IMG: Debian Logo]

Red Hat/Rocky/AlmaLinux
[IMG: Red Hat Logo]

SUSE
[IMG: SUSE Logo]

Ubuntu
[IMG: Ubuntu Logo]

Other Linux
[IMG: Linux Logo]

Select your BSD operating system:
OpenBSD
[IMG: OpenBSD Logo]
FreeBSD
[IMG: FreeBSD Logo]
NetBSD
[IMG: NetBSD Logo]
[H3] Source code
The source code can be found in the main file browser
or you can access the source control repository directly
at git.postgresql.org.
Instructions for building from source can be found in the
documentation.
[H3] Beta/RC Releases and development snapshots (unstable)
There are source code and binary packages
of beta and release candidates, and of the current development code available
for testing and evaluation of new features. Note that these builds should
be used for testing purposes only, and not for production systems.
[H2] Additional Software
[H3] Software Catalogue
There is much software available that is not bundled with PostgreSQL. The Software
Catalogue offers a listing of many commercial and Open Source applications, interfaces and extensions to PostgreSQL
that you may find useful.
If you wish to have your product listed in the catalogue, please fill out this form.
[H2] File Browser
You can download most of the software we publish from a mirror site using our File Browser.

[H2] Quick Links

About

Governance

Policies

Feature Matrix

Donate

History

Sponsors

Contributing
Financial
Servers

Latest News

Upcoming Events

Past events

Press

Licence

[H1] PostgreSQL 19 Beta 1 Released!
Posted on 2026-06-04 by PostgreSQL Global Development Group
PostgreSQL Project
The PostgreSQL Global Development Group announces that the first beta release of
PostgreSQL 19 is now available for download.
This release contains PostgreSQL 19 feature previews ahead of general
availability, though some details of the release can change during the beta
period.
You can find information about all of the PostgreSQL 19 features and changes in
the release notes:
https://www.postgresql.org/docs/19/release-19.html
In the spirit of the open source PostgreSQL community, we strongly encourage you
to test the new features of PostgreSQL 19 on your systems to help us eliminate
bugs and other issues. While we do not advise you to run beta versions in
production environments, we encourage you to find ways to run your typical
application workloads against this beta release.
Your testing and feedback help the community ensure that PostgreSQL 19
upholds our standards of delivering a stable, reliable release of the
world's most advanced open source relational database. Please read more about
our beta testing process and how
you can contribute:
https://www.postgresql.org/developer/beta/
[H2] PostgreSQL 19 Feature Highlights
Below are some of the feature highlights that are planned for PostgreSQL 19.
This list is not exhaustive; for the full list of planned features, please see
the release notes.
[H3] Performance
PostgreSQL 19 builds on the asynchronous I/O subsystem introduced in
PostgreSQL 18. In this release, io_method=worker now automatically scales the
number of I/O workers based on the new
io_min_workers
and
io_max_workers
settings.
This release also introduces the
pg_plan_advice
extension, which lets users stabilize and control planner decisions, along with
pg_stash_advice
to apply advice automatically using query identifiers.
This release brings improvements to vacuum and maintenance operations.
Autovacuum can now use parallel workers, which can be configured with the new
autovacuum_max_parallel_workers
setting, and a new autovacuum scoring system
helps prioritize tables to vacuum. PostgreSQL 19 further enhances vacuum with
a new strategy that can automatically reduce future vacuuming work by marking
pages as visible while they're being queried. Additionally, this release
adds the new REPACK
command and its nonblocking CONCURRENTLY
option, which allow tables to be rebuilt with less operational overhead.
PostgreSQL 19 shows up to 2x better performance on inserts when foreign key
checks are present. Additionally, this release improves several areas of
the query planner and executor, including new anti-join optimizations, broader
use of incremental sorts,
eager aggregation
that speeds up row processing,
faster reads from storage during parallel sequential scans, and
simplification of IS DISTINCT FROM
and IS NOT DISTINCT FROM to plain
<> and = operators when the inputs are not nullable. There are also
improvements for
LISTEN/NOTIFY
scalability that impact multi-channel workloads.
[H3] Developer Experience
PostgreSQL 19 introduces support for
SQL/PGQ,
letting users execute property graph queries using SQL standard syntax. This
release also expands temporal query capabilities with UPDATE and DELETE
support for the
FOR PORTION OF
clause, complementing the temporal constraint support added in
PostgreSQL 18. This release also adds
ALTER TABLE ... MERGE PARTITIONS
and ALTER TABLE ... SPLIT PARTITIONS to make it easier to reorganize
partitioned tables in place. There is now also support for returning rows that
conflict during an upsert operation using
INSERT ... ON CONFLICT DO SELECT ... RETURNING.
PostgreSQL 19 introduces the new
GROUP BY ALL
syntax, making it easy to add
all non-aggregate and non-window output columns as part of the grouping. This
release extends string processing capabilities in
jsonpath
with the addition of
lower(), upper(), initcap(), replace(), split_part(), and the trim()
family of functions.
PostgreSQL 19 makes it easier to adopt "read-your-writes" query patterns
when working with replicas using the new
WAIT FOR LSN
command. This lets a
session wait until changes up to a specific log position (LSN) have been
replayed on the replica before executing a SELECT query.
PostgreSQL 19 also adds new SQL functions to retrieve the
DDL statements
needed to recreate roles, tablespaces, and databases, simplifying
scripting and migration tasks. Additionally, the
random()
function now works
with date and timestamp types, and
PL/Python
now supports event triggers.
[H3] Security Features
PostgreSQL 19 adds server-side support for Server Name Indication (SNI) through
a new
pg_hosts.conf
file, allowing a single PostgreSQL server to present
different TLS certificates based on the hostname requested by the client. There
is also a new
password_expiration_warning_threshold
setting (defaulting to 7 days) to warn users in advance of upcoming password
expirations.
Further to the ongoing deprecation efforts of
md5 authentication,
this release
issues a warning to the client after a successful md5 authentication. This is
controllable via the new
md5_password_warnings
setting.
[H3] Monitoring and Observability
PostgreSQL 19 introduces the
pg_stat_lock
view, which reports per-lock-type
statistics, and
pg_stat_recovery
which provides detailed visibility into the
state of recovery operations. A stats_reset column is now available across
many statistics views to show when counters were last cleared. The
pg_stat_progress_vacuum
and
pg_stat_progress_analyze
views now include a
started_by column that reports the initiator of the operation, and
pg_stat_progress_vacuum also has a mode column that reports how vacuum
is operating.
This release also allows
log_min_messages
levels to be specified per process
type, giving operators finer control over what each part of the system logs.
Additionally, WAL full page write byte counts are now reported in
VACUUM and
ANALYZE log output,
helping identify maintenance operations that generate large amounts of WAL.
Additionally, EXPLAIN ANALYZE
now supports surfacing asynchronous I/O (AIO) statistics through its IO option,
providing better visibility into how queries are using the AIO subsystem.
[H3] Logical Replication and Query Federation
In PostgreSQL 19, logical replication now replicates sequence values,
simplifying tasks like online upgrades. Additionally, the new
CREATE PUBLICATION ... EXCEPT
syntax allows you to publish all tables in
a database except for a specified set, while
CREATE SUBSCRIPTION ... SERVER
allows subscriptions to be defined using a foreign server, simplifying
credential management.
PostgreSQL 19 makes it possible to enable logical replication without restarting
a server. Logical replication can now be enabled on demand even when
wal_level
is set to replica, and the new read-only
effective_wal_level
parameter reports the WAL level currently in effect. This reduces the need to
commit upfront to a higher WAL level for clusters that may only occasionally
need it, and avoids disrupting an active workload.
The PostgreSQL foreign data wrapper,
postgres_fdw,
used for query federation, includes several performance improvements, including
pushing down array operations to the remote server, and retrieving and using
statistics from foreign tables to support better local query planning.
[H3] Other Highlights
The PostgreSQL 19 beta period includes a temporary "grease mode"
to try to find protocol compatibility problems in the wider ecosystem. This wiki
page contains information on how the campaign works:
https://wiki.postgresql.org/wiki/Grease
PostgreSQL 19 allows
data checksums
to be enabled or disabled online, without
requiring a cluster restart or reinitialization.
There are several notable changes to be aware of in
PostgreSQL 19.
Just-in-time compilation (JIT)
is now disabled by default,
and the
default_toast_compression
setting now defaults to lz4,
providing better default compression and decompression performance. Support for
RADIUS authentication is now removed. Additionally, the
vacuumdb --analyze-only
command by default analyzes partitioned tables.
[H2] Additional Features
Many other new features and improvements have been added to PostgreSQL 19. Many
of these may also be helpful for your use cases. Please see the
release notes for a
complete list of new and changed features:
https://www.postgresql.org/docs/19/release-19.html
[H2] Testing for Bugs & Compatibility
The stability of each PostgreSQL release greatly depends on you, the community,
to test the upcoming version with your workloads and testing tools to find bugs
and regressions before the general availability of PostgreSQL 19. As this is a
Beta, minor changes to database behaviors, feature details, and APIs are still
possible. Your feedback and testing will help determine the final tweaks on the
new features, so please test in the near future. The quality of user testing
helps determine when we can make a final release.
A list of open issues
is publicly available in the PostgreSQL wiki. You can
report bugs using this form on
the PostgreSQL website:
https://www.postgresql.org/account/submitbug/
[H2] Beta Schedule
This is the first beta release of version 19. The PostgreSQL Project will
release additional betas as required for testing, followed by one or more
release candidates, until the final release around September/October 2026. For further
information please see the Beta Testing
page.
[H2] Links
Download
Beta Testing Information
PostgreSQL 19 Beta Release Notes
PostgreSQL 19 Open Issues
Submit a Bug
Donate

[H2] Quick Links

Support

Versioning Policy

Security

Professional Services

Hosting Solutions

Report a Bug

[H1] Versioning Policy
The PostgreSQL Global Development Group releases a new major version containing
new features about once a year. Each major version receives bug fixes and, if
need be, security fixes that are released at
least once every three months in what we call a "minor release." For more
information on the minor release schedule, you can view the
minor release roadmap.
If the release team determines that a critical bug or security fix is too
important to wait until the regularly scheduled minor release, it may make
a release available outside of the minor release roadmap.
The PostgreSQL Global Development Group supports a major version for 5 years
after its initial release. After this, a final minor version will be released
and the software will then be unsupported (end-of-life).
[H2] Version Numbering
Starting with PostgreSQL 10, a major version is indicated by increasing the
first part of the version, e.g. 10 to 11. Before PostgreSQL 10, a major version
was indicated by increasing either the first or second part of the version
number, e.g. 9.5 to 9.6.
Minor releases are numbered by increasing the last part of the version number.
Beginning with PostgreSQL 10, this is the second part of the version number,
e.g. 10.0 to 10.1; for older versions this is the third part of the version
number, e.g. 9.5.3 to 9.5.4.
[H2] Upgrading
Major versions make complex changes, so the contents of the data directory
cannot be maintained in a backward compatible way. A dump/reload of the
database or use of the
pg_upgrade application is required
for major upgrades. We also recommend reading the
upgrading section of the major
version you are planning to upgrade to. You can upgrade from one major version
to another without upgrading to intervening versions, but we recommend reading
the release notes of all intervening major
versions prior to doing so.
Minor release upgrades do not require a dump and restore; you simply stop
the database server, install the updated binaries, and restart the server.
Such upgrades might require additional steps so always read
the release notes first.
Minor releases only contain fixes for frequently-encountered bugs,
low-risk fixes, security issues, and
data corruption problems. The community considers performing minor
upgrades to be less risky than continuing to run an old minor version.

We recommend that users always run the current minor release associated
with their major version.
[H2] Releases

Version
Current minor
Supported
First Release
Final Release

18
18.4
Yes
September 25, 2025
November 14, 2030

17
17.10
Yes
September 26, 2024
November 8, 2029

16
16.14
Yes
September 14, 2023
November 9, 2028

15
15.18
Yes
October 13, 2022
November 11, 2027

14
14.23
Yes
September 30, 2021
November 12, 2026

13
13.23
No
September 24, 2020
November 13, 2025

12
12.22
No
October 3, 2019
November 21, 2024

11
11.22
No
October 18, 2018
November 9, 2023

10
10.23
No
October 5, 2017
November 10, 2022

9.6
9.6.24
No
September 29, 2016
November 11, 2021

9.5
9.5.25
No
January 7, 2016
February 11, 2021

9.4
9.4.26
No
December 18, 2014
February 13, 2020

9.3
9.3.25
No
September 9, 2013
November 8, 2018

9.2
9.2.24
No
September 10, 2012
November 9, 2017

9.1
9.1.24
No
September 12, 2011
October 27, 2016

9.0
9.0.23
No
September 20, 2010
October 8, 2015

8.4
8.4.22
No
July 1, 2009
July 24, 2014

8.3
8.3.23
No
February 4, 2008
February 7, 2013

8.2
8.2.23
No
December 5, 2006
December 5, 2011

8.1
8.1.23
No
November 8, 2005
November 8, 2010

8.0
8.0.26
No
January 19, 2005
October 1, 2010

7.4
7.4.30
No
November 17, 2003
October 1, 2010

7.3
7.3.21
No
November 27, 2002
November 27, 2007

7.2
7.2.8
No
February 4, 2002
February 4, 2007

7.1
7.1.3
No
April 13, 2001
April 13, 2006

7.0
7.0.3
No
May 8, 2000
May 8, 2005

6.5
6.5.3
No
June 9, 1999
June 9, 2004

6.4
6.4.2
No
October 30, 1998
October 30, 2003

6.3
6.3.2
No
March 1, 1998
March 1, 2003

[H2] Quick Links

Community

Contributors

Mailing Lists

IRC

Local User Groups

Recognised NPOs

Events

International Sites

[H1] Community

PostgreSQL is well-supported by its active community. There are more than a dozen mailing lists available, categorized into topics like:

Announcements
PostgreSQL development
General PostgreSQL Support
Jobs

and more. We also have many local PostgreSQL User Groups all over the world, and there is also an active IRC community.

There are also links to international sites that contain PostgreSQL information in various languages.
People in the PostgreSQL community also contribute to:
Planet PostgreSQL, an aggregator of blogs covering many topics around PostgreSQL
PostgreSQL Wiki, our wiki, hosting user generated content as well as information for how to contribute code to PostgreSQL

[H2] Planet PostgreSQL

Christophe Pettus: All Your GUCs in a Row: the debug_* family

Richard Yen: PGDay Boston 2026

Richard Yen: PGDay Boston 2026

Christophe Pettus: All Your GUCs in a Row: deadlock_timeout

Cornelia Biacsics: Contributions for week 22, 2026

Christoph Berg: PGConf.dev 2026 in Vancouver

Christophe Pettus: All Your GUCs in a Row: DateStyle

More

[H2] External Resources

pg-forum.de, a German PostgreSQL forum.

Please send appropriate links to
pgsql-www@lists.postgresql.org
for possible inclusion on this page. Note that
pgsql-www@lists.postgresql.org
is a publicly archived mailing list.

[H2] Quick Links

About

Governance

Policies

Feature Matrix

Donate

History

Sponsors

Contributing
Financial
Servers

Latest News

Upcoming Events

Past events

Press

Licence

[H1] About
[IMG: PostgreSQL Elephant Logo]
[H2] What is PostgreSQL?
PostgreSQL is a powerful, open source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads. The origins of PostgreSQL date back to 1986 as part of the POSTGRES project at the University of California at Berkeley and has nearly 40 years of active development on the core platform.
PostgreSQL has earned a strong reputation for its proven architecture, reliability, data integrity, robust feature set, extensibility, and the dedication of the open source community behind the software to consistently deliver performant and innovative solutions. PostgreSQL runs on all major operating systems, has been ACID-compliant since 2001, and has powerful add-ons such as the popular PostGIS geospatial database extender. It is no surprise that PostgreSQL has become the open source relational database of choice for many people and organisations.
Getting started with using PostgreSQL has never been easier - pick a project you want to build, and let PostgreSQL safely and robustly store your data.
[H2] Why use PostgreSQL?
PostgreSQL comes with many features aimed to help developers build applications, administrators to protect data integrity and build fault-tolerant environments, and help you manage your data no matter how big or small the dataset. In addition to being free and open source, PostgreSQL is highly extensible. For example, you can define your own data types, build out custom functions, even write code from different programming languages without recompiling your database!
PostgreSQL tries to conform with the SQL standard where such conformance does not contradict traditional features or could lead to poor architectural decisions. Many of the features required by the SQL standard are supported, though sometimes with slightly differing syntax or function. Further moves towards conformance can be expected over time. As of the version 18 release in September 2025, PostgreSQL conforms to at least 170 of the 177 mandatory features for SQL:2023 Core conformance. As of this writing, no relational database meets full conformance with this standard.
Below is an inexhaustive list of various features found in PostgreSQL, with more being added in every major release:
Data Types
Primitives: Integer, Numeric, String, Boolean
Structured: Date/Time, Array, Range / Multirange, UUID
Document: JSON/JSONB, XML, Key-value (Hstore)
Geometry: Point, Line, Circle, Polygon
Customizations: Composite, Custom Types

Data Integrity
UNIQUE, NOT NULL
Primary Keys
Foreign Keys
Exclusion Constraints
Explicit Locks, Advisory Locks

Concurrency, Performance
Indexing: B-tree, Multicolumn, Expressions, Partial
Advanced Indexing: GiST, SP-Gist, KNN Gist, GIN, BRIN, Covering indexes, Bloom filters
Sophisticated query planner / optimizer, index-only scans, multicolumn statistics
Transactions, Nested Transactions (via savepoints)
Multi-Version concurrency Control (MVCC)
Parallelization of read queries and building B-tree indexes
Table partitioning
All transaction isolation levels defined in the SQL standard, including Serializable
Just-in-time (JIT) compilation of expressions
Asynchronous I/O (AIO)

Reliability, Disaster Recovery
Write-ahead Logging (WAL)
Replication: Asynchronous, Synchronous, Logical
Point-in-time-recovery (PITR), active standbys
Tablespaces

Security
Authentication: GSSAPI, SSPI, LDAP, SCRAM-SHA-256, Certificate, OAuth 2.0, and more
Robust access-control system
Column and row-level security
Multi-factor authentication with certificates and an additional method

Extensibility
Stored functions and procedures
Procedural Languages: PL/pgSQL, Perl, Python, and Tcl. There are other languages available through extensions, e.g. Java, JavaScript (V8), R, Lua, and Rust
SQL/JSON constructors, query functions, path expressions, and JSON_TABLE
Foreign data wrappers: connect to other databases or streams with a standard SQL interface
Customizable storage interface for tables
Many extensions that provide additional functionality, including PostGIS

Internationalisation, Text Search
Support for international character sets, e.g. through ICU collations
Case-insensitive and accent-insensitive collations
Full-text search

There are many more features that you can discover in the PostgreSQL documentation. Additionally, PostgreSQL is highly extensible: many features, such as indexes, have defined APIs so that you can build out with PostgreSQL to solve your challenges.
PostgreSQL has been proven to be highly scalable both in the sheer quantity of data it can manage and in the number of concurrent users it can accommodate. There are active PostgreSQL clusters in production environments that manage many terabytes of data, and specialized systems that manage petabytes.
[H2] Any questions?
The first place to go to for any questions on PostgreSQL is its world-renowned documentation, which discusses how to use PostgreSQL in-depth.
We also have many mailing lists where you can connect and participate in the community. There are also many events and local user groups where you can connect with other PostgreSQL users.
[H2] Our users us

[Our customers] expect both high performance and high availability from our software, central part of which is the SQL database engine. And we have found that the PostgreSQL is really up to the task.
Maksym Sobolyev, SippySoft Inc.

Quorum commit for synchronous replication in PostgreSQL 10 gives more options to extend our ability to promote database infrastructure with nearly zero downtime from the application perspective. This allows us to continuously deploy and update our database infrastructure without incurring long maintenance windows.
Curt Micol, Simple Finance

Under loads heavy and light, with virtually no administration overhead, PostgreSQL chugs along and "just works".
Benjamin Smith, CTO, Charterworks

We use PostgreSQL on all LeapServs to track information ranging from a couple hundred thousand rows to 20+ million.
Lindsay Snider, Founding Partner, BitLeap LLC

We keep up with the latest development of PostgreSQL since 2010 ... and every new release brings us more performance and usability improvements that we take advantage of practically from day one.
Valentine Gogichashvili, Zalando Technologies

[H2] What's a database project without statistics?

[H3] 35+ Years Development

[H3] 725+ Contributors

[H3] 61,000+ Commits

[H3] 70+ Local User Groups

[H3] 1,780,000+ Lines of C

[H3] 720+ Events

[H3] Millions of Happy Users

[H3] ∞ Data Stored