PostgreSQL® 19 is generally available from 19 November 2026, and Aiven for PostgreSQL® gives you full production support from day one so you can capitalize on the latest innovations. This release makes table maintenance non-blocking, gives builders control over query plans and moves more extension installs onto PostgreSQL's own trust model on the Aiven platform. With this release, you can eliminate planned maintenance windows for table cleanup, prevent sudden query regressions with pinned execution plans and manage extensions natively will full ownership. You also get faster out-of-the-box throughput, consistent read-scaling on replicas and zero-downtime replication setups, all backed by Aiven’s fully-managed reliability.
What's new in PostgreSQL 19: more speed, less downtime, predictable scale
Reclaim table bloat without blocking
REPACK replaces VACUUM FULL and CLUSTER. By runningREPACK (CONCURRENTLY) you can compact bloated tables and reclaim wasted storage while your application’s reads and writes continue uninterrupted. Builders no longer must schedule a maintenance window to clean up a bloated table.
Stabilize query plans and eliminate unexpected latency spikes with pg_plan_advice
pg_plan_advice lets you pin planner decisions so queries behave predictably under changing data volumes. pg_stash_advice stores advice and applies it by query identifier, giving you fine-grained performance stability without rewriting application code.
Keep autovacuum ahead on busy systems to keep high-throughput workloads running smoothly
Autovacuum can vacuum indexes in parallel using autovacuum_max_parallel_workers, and it now scores tables by urgency, preventing transaction ID wraparound and table bloat from slowing you down.. The new views pg_stat_autovacuum_scores and pg_stat_lock show what autovacuum prioritizes and where locks wait, reducing troubleshooting time.
Read your writes on standbys
WAIT FOR LSN lets a session wait until a standby has replayed a given WAL position, so reads on a replica see your latest writes. This lets your users immediately read their own writes while you maximize your cluster's read capacity.
Get or create in one round trip
INSERT ... ON CONFLICT DO SELECT ... RETURNING returns the existing row when a conflict occurs, so get-or-create takes one statement. This reduces network round-trips, eliminates race conditions and keeps application logic cleaner.
Logical replication without a restart
The effective WAL level rises to logical when you create the first logical replication slot, so no restart is needed. This supports operational and replication continuity across your database cluster and downstream pipelines. Publications also support FOR ALL SEQUENCES.
Security and defaults
- PostgreSQL 19 supports the Server Name Indication (SNI)TLS extension, enabling hostname-based certificate selection and connection routing.
- md5 password logins now raise a warning, giving teams passive, zero-downtime visibility into legacy credentials before MD5 support is completely removed. Our MD5 to SCRAM migration guide covers existing users.
- Just-In-Time (JIT) compilation is off by default, protecting OLTP workloads from CPU spikes, memory bloat and unpredictable latency.
- Foreign key checks are faster, and bulk inserts run nearly 2x faster in community testing.
Move faster with trusted extensions on PostgreSQL 19 services
Aiven for PostgreSQL 19 embraces PostgreSQL’s native trusted extension framework, replacing custom platform workarounds with standard PostgreSQL behavior. On PostgreSQL 19 services, more extensions install through PostgreSQL's own trusted extension mechanism instead of Aiven's extension allowlist. An extension marked trusted is one its author declares safe for non-superusers to install. PostgreSQL then enforces who can install it, in place of a custom Aiven hook.
What this means for builders:
-
Installing uses the same command. Run
CREATE EXTENSIONas you do today. Any user with theCREATEprivilege on the database can install a trusted extension. The PostgreSQL documentation explains:[…] if the extension is marked trusted in its control file, then it can be installed by any user who has
CREATEprivilege on the current database. In this case the extension object itself will be owned by the calling user, but the contained objects will be owned by the bootstrap superuser (unless the extension's script explicitly assigns them to the calling user). This configuration gives the calling user the right to drop the extension, but not to modify individual objects within it. -
Other extensions keep their current route. Extensions that cannot be marked trusted still install through the allowlist.
-
Earlier versions do not change. PostgreSQL 18 and older services keep their current behavior.
To see which extensions are trusted on your PostgreSQL 19 service, run:
Loading code...
Update your extensions to support PostgreSQL 19
PostgreSQL 19 launches with the extensions whose upstream releases support it. Extensions still waiting on an upstream release follow as those releases ship. Run SELECT name, default_version FROM pg_available_extensions; on your service to see what is available today.
Before a major version upgrade, update your extensions to versions that support PostgreSQL 19, then fork the service and test the upgrade on the fork. The extension versions per PostgreSQL release page shows what each PostgreSQL version supports, and the supported extensions page describes each extension.
Get building today
Create a service and set the version to 19 to try PostgreSQL 19 on Aiven. Follow our events page and LinkedIn for upcoming deep dives on the new features.
Table of contents
- What's new in PostgreSQL 19: more speed, less downtime, predictable scale
- Reclaim table bloat without blocking
- Stabilize query plans and eliminate unexpected latency spikes with pg_plan_advice
- Keep autovacuum ahead on busy systems to keep high-throughput workloads running smoothly
- Read your writes on standbys
- Get or create in one round trip
- Logical replication without a restart
- Security and defaults
- Move faster with trusted extensions on PostgreSQL 19 services
- Update your extensions to support PostgreSQL 19
- Get building today

