PostgreSQL 19 Beta 1 Lands With Parallel Autovacuum, Self-Scaling Async I/O, and a Planner-Hint Extension
PostgreSQL 19 Beta 1, released June 4, brings parallel autovacuum, self-scaling async I/O workers, a new pg_plan_advice planner extension, SQL/PGQ graph queries, and turns JIT off by default. GA is targeted for September/October 2026.
Overview
The PostgreSQL Global Development Group released the first beta of PostgreSQL 19 on June 4, 2026, opening the testing phase for the next major version of the open-source relational database, according to the project’s release announcement. The release builds on the asynchronous I/O subsystem introduced in PostgreSQL 18 and adds parallel autovacuum, a new planner-control extension, SQL-standard property graph queries, and a set of changes to long-standing defaults — including disabling just-in-time compilation out of the box.
The announcement marks the start of the beta cycle, not a production-ready release. The PostgreSQL Project said it will issue additional betas as needed, followed by one or more release candidates, with the final release targeted for around September or October 2026.
Performance and Maintenance
Several of the headline changes target the maintenance and I/O paths that operators tune most often.
The asynchronous I/O subsystem added in PostgreSQL 18 gains automatic scaling in this release. According to the PostgreSQL announcement, io_method=worker now automatically scales the number of I/O workers based on the new io_min_workers and io_max_workers settings, rather than relying on a single fixed worker count.
Autovacuum — the background process that reclaims space from updated and deleted rows — can now run in parallel. The release notes state that autovacuum can use parallel workers, configured through the new autovacuum_max_parallel_workers setting, and that a new autovacuum scoring system helps prioritize which tables to vacuum. The same release adds a new REPACK command, with a nonblocking CONCURRENTLY option, that allows tables to be rebuilt with less operational overhead, per the announcement.
On the write path, the project reports that PostgreSQL 19 shows up to 2x better performance on inserts when foreign key checks are present, according to the PostgreSQL announcement. Linux Compatible similarly described foreign-key inserts as showing up to double the throughput.
Planner Control and New SQL Features
PostgreSQL 19 introduces the pg_plan_advice extension, which lets users stabilize and control planner decisions, alongside a companion pg_stash_advice that applies advice automatically using query identifiers, the announcement states. The release also improves several areas of the query planner and executor, including new anti-join optimizations and broader use of incremental sorts.
The release adds support for SQL/PGQ, the SQL-standard syntax for property graph queries, according to the PostgreSQL announcement, letting users run graph-style queries against relational data. Other developer-facing additions described in the announcement include ALTER TABLE ... MERGE PARTITIONS and ALTER TABLE ... SPLIT PARTITIONS for reorganizing partitioned tables in place, a new GROUP BY ALL syntax, and a WAIT FOR LSN command that lets a session wait until changes up to a specific log position have been replayed on a replica before running a SELECT, supporting read-your-writes patterns against replicas.
Replication, Security, and Observability
Logical replication receives several changes. In PostgreSQL 19, logical replication now replicates sequence values, which the announcement notes simplifies tasks like online upgrades. The release also makes it possible to enable logical replication without restarting a server, allowing it to be turned on even when wal_level is set to replica.
On the security side, the release adds server-side support for Server Name Indication through a new pg_hosts.conf file, allowing a single server to present different TLS certificates based on the hostname a client requests, according to the announcement. It also issues a warning to the client after a successful md5 authentication as part of the ongoing deprecation of that method, controllable via the new md5_password_warnings setting.
For monitoring, PostgreSQL 19 introduces the pg_stat_lock view, which reports per-lock-type statistics, and pg_stat_recovery, which provides visibility into recovery operations, the announcement states. EXPLAIN ANALYZE can now surface asynchronous I/O statistics through its IO option.
Changed Defaults
A few long-standing defaults change in this release. According to the PostgreSQL announcement, just-in-time compilation is now disabled by default, the default_toast_compression setting now defaults to lz4, and support for RADIUS authentication is removed. Linux Compatible characterized the JIT change as shipping disabled by default “after years of mixed results in production environments” and flagged the RADIUS removal as a breaking change for administrators to check before upgrading.
The release also allows data checksums to be enabled or disabled online, without requiring a cluster restart or reinitialization, per the announcement.
What We Don’t Know
As a beta, the feature set and behavior are not final. The PostgreSQL Project said additional betas and release candidates will follow before general availability, and the announcement frames the September/October 2026 window as approximate. Performance figures such as the foreign-key insert improvement are drawn from the project’s own announcement and have not yet been independently benchmarked at general availability. Linux Compatible cautioned that running beta software in production remains inadvisable without staging infrastructure that mirrors live workloads.
The beta arrives weeks after the project’s most recent maintenance cycle, when PostgreSQL shipped a coordinated security release fixing 11 CVEs across its five supported major versions. Administrators evaluating PostgreSQL 19 are encouraged to test against representative workloads and report issues through the project’s bug-submission form during the beta period.