Databricks Ships PostgreSQL 19 on Lakebase and Neon at Launch
Databricks rolled PostgreSQL 19 into Lakebase and Neon on release day, November 19, 2026, bringing REPACK table rebuilds, plan-stability extensions and the WAIT FOR LSN replica command.
By Amara Osei
3 min read

What's News
- Databricks added PostgreSQL 19 to Lakebase and Neon on the release date, November 19, 2026.
- REPACK rebuilds tables to reclaim disk space but still needs an exclusive lock for the final file swap, per Neon's release notes.
- New pg_plan_advice and pg_stash_advice extensions stabilize query plans without rewriting application code.
- WAIT FOR LSN lets applications wait for a replica's write-ahead log position to guarantee fresh reads.
- Lakebase engineers contributed upstream work on query-plan advice, shared memory and release management.
By Amara Osei
Databricks added PostgreSQL 19 to Lakebase and Neon on the day the open-source project released the new version, November 19, 2026, according to the company and the PostgreSQL community announcement. That gives managed-database customers immediate access to the release's new maintenance, query-planning and replication tooling.
The upgrade matters for teams building AI applications even though it ships no new model or vector index. Operational databases sit behind the user-facing parts of those systems. They store conversation history, track jobs and permissions, record application events and serve calls that need predictable response times. A database change that makes this layer easier to maintain can outweigh a new feature in the application layer.
What does PostgreSQL 19 change?
The headline addition is REPACK, a command that rebuilds a table to reclaim unused space and can optionally reorder data to match an index. PostgreSQL creates a new row version whenever data changes. Routine vacuuming makes old space reusable, but it doesn't always shrink the table on disk. A table holding frequently updated jobs or messages can keep occupying more space than its live rows need.
One option lets ordinary reads and writes continue through most of the rebuild. The operation isn't free of disruption. As Neon's release notes explain, PostgreSQL still needs an exclusive lock to finish swapping the rebuilt files into place. Teams should test under a representative write load rather than assume the final lock is negligible on a busy table.
The release also adds two extensions for plan stability:
- pg_plan_advice — tests and stabilizes execution plans.
- pg_stash_advice — applies stored advice to a matching query.
The planner ordinarily picks an execution path based on available data and statistics. When that choice changes, a query that used to be fast can suddenly turn slow. The new tools let operators investigate or mitigate the regression without immediately rewriting application code. Any saved advice should be revisited as data and workloads evolve.
Why does replica timing matter?
PostgreSQL 19 adds WAIT FOR LSN, which lets an application wait for a replica to reach a specified position in the write-ahead log. With asynchronous replication, a write succeeds on the primary before the replica has applied it. A user or agent reading from that replica right away may see an earlier state.
The lag matters when, say, an application records approval for a task and immediately asks another service to read it from a replica. Waiting for the relevant log position lets that read see the approval. The feature trades waiting time for freshness when the workflow demands it, instead of assuming all replica reads are current.
What can teams try today?
Databricks' supported-versions documentation lists PostgreSQL 19 for Lakebase, and Neon's announcement explains how to select it for a new project. Neither announcement says existing databases were upgraded automatically. Databricks also says Lakebase engineers contributed to the upstream release, including work on query-plan advice, shared memory and release management.
For teams weighing a migration, version availability is only the starting point. The practical checklist: run representative queries, confirm extension compatibility, measure replica lag and rehearse the maintenance operations that prompted the upgrade in the first place. Compare those results against current database behavior before moving production traffic.
Source: unite.ai
More from Amara Osei
Show full bio
Senior reporter covering companies, deals and strategy in entrepreneurship, startups and venture funding at Business Bearings.
2,503 articles