PostgreSQL 19 Beta 2 is a map of where the new features are still wet

The PostgreSQL Global Development Group released the second beta of PostgreSQL 19 on 16 July — in its own words, it "announces that the second beta release of PostgreSQL 19 is now available for download." The announcement is a list of fourteen fixes, and read the right way it is the most informative document of the cycle so far: the fixes cluster exactly where 19's new surface area is.

The fix list is a feature map

Of the fourteen changes, five land squarely on features that did not exist before this release. Each line verbatim from the announcement:

Several fixes for the new FOR PORTION OF temporal table syntax.
Several fixes for the new SQL/PGQ property graph feature.
Fix REPACK worker not being cleaned up on a FATAL exit.
Fix race condition when logical decoding activation is concurrently interrupted.
Disallow negative values for max_retention_duration.

"Several fixes" against both FOR PORTION OF and SQL/PGQ is the tell: the temporal-table and property-graph work is where the paint is still wet — which is precisely what a beta cycle is for.

One quiet revert

One line changes behaviour between betas rather than repairing it: "Revert non-text output formats for pg_dumpall." If you tried Beta 1 and scripted against a non-text pg_dumpall dump, that capability is gone in Beta 2. It is the clearest reminder in the list that beta features can be withdrawn, not just fixed.

What 19 ships when it ships

The headline features, as the project described them in the Beta 1 announcement of 4 June:

• Property graphs. "PostgreSQL 19 introduces support for SQL/PGQ, letting users execute property graph queries using SQL standard syntax."
• Temporal writes. The release "expands temporal query capabilities with UPDATE and DELETE support for the FOR PORTION OF clause, complementing the temporal constraint support added in PostgreSQL 18."
• Table rebuilds. 19 "adds the new REPACK command and its nonblocking CONCURRENTLY option, which allow tables to be rebuilt with less operational overhead."
• Logical replication without a restart. "Logical replication can now be enabled on demand even when wal_level is set to replica," with a new read-only effective_wal_level parameter reporting what is actually in effect. Sequence values now replicate, CREATE PUBLICATION ... EXCEPT publishes every table but a named set, and CREATE SUBSCRIPTION ... SERVER defines a subscription against a foreign server.
• Faster inserts. "PostgreSQL 19 shows up to 2x better performance on inserts when foreign key checks are present."

The caveat, in the project's own words

As this is a Beta, minor changes to database behaviors, feature details, and APIs are still possible.

PostgreSQL Global Development Group, Beta 2 announcement

Moving between betas is a major-version upgrade: the project says to use "a strategy similar to upgrading between major versions of PostgreSQL (e.g. pg_upgrade or pg_dump / pg_restore)." More betas follow as needed, then release candidates, "until the final release around September/October 2026." Bugs go through the report form.

Primary sources: PostgreSQL 19 Beta 2 Released!, PostgreSQL 19 Beta 1 Released!, read 2026-07-30.