Lakebase UI lets users spin up a PostgreSQL 19 project instantly, a day after the community release.
*PostgreSQL 19 reaches GA today and is instantly available on Databricks' Lakebase. The rollout sidesteps the weeks‑long lag typical of managed services, giving customers immediate access to new operational controls.*
PostgreSQL 19 hit general availability today, and Databricks' Lakebase made it accessible to customers the same day. The rapid rollout bypasses the weeks‑long lag typical of managed PostgreSQL services. Lakebase engineers, who sit on the PostgreSQL committers list, integrated the release directly, offering a new project option that selects version 19 at creation.
The release is not about a single headline feature. Instead it attacks the operational headaches that database teams wrestle with: table bloat, unstable plans, replica lag, and risky maintenance. The added commands—REPACK, query‑plan advice, and WAIT FOR LSN—promise more hands‑on control without sacrificing PostgreSQL’s reliability bias.
PostgreSQL 19 reached general availability today and is already live on Lakebase. Databricks made the version selectable when creating a new Lakebase project, eliminating the usual weeks‑long wait for managed PostgreSQL services. Several Lakebase engineers are active PostgreSQL committers and contributors; they worked on this release from query‑plan advice to shared memory and release management. The company’s goal was to give customers access the same day the community released the code. This fast‑track approach reflects Lakebase’s deep integration with the PostgreSQL core development process.
PostgreSQL 19 adds a built‑in REPACK command that reclaims space while normal reads and writes continue. Traditional tools like VACUUM FULL or CLUSTER lock the table for the entire operation, halting traffic. REPACK uses a CONCURRENTLY mode: it rebuilds the table in the background, captures ongoing changes via logical decoding, then briefly takes an ACCESS EXCLUSIVE lock to swap the new files into place. The command can also order rows with USING INDEX, matching CLUSTER’s physical ordering without downtime. REPACK therefore turns a historically disruptive maintenance task into a near‑online operation, addressing table bloat that accumulates from heavy UPDATE and DELETE activity.
PostgreSQL 19 introduces pg_plan_advice and pg_stash_advice to let administrators nudge the optimizer when statistics mislead it. The cost‑based planner relies on per‑table statistics, which can miss cross‑table correlations such as a tiny customer segment generating a large share of orders. With pg_plan_advice, users can describe a preferred join strategy; the system records whether the advice was followed. pg_stash_advice stores advice by query ID and automatically applies it on future planning. These tools do not replace the planner or add new statistics; they simply provide a manual override path for cases where the default plan would be inefficient.
Concurrent REPACK creates an extra replication slot for the operation’s duration, requiring free capacity under max_repack_replication_slots. It also needs temporary disk space for a copy of the table and its indexes, potentially plus a sort file as large as the table itself. Tables with heavy update or delete traffic hit a hard ceiling: the current implementation aborts if more than about 104 million tuples are modified while REPACK (CONCURRENTLY) runs. The target table must have a non‑deferrable primary key or a suitable index‑based replica identity. Long‑running transactions can delay the final lock, and snapshots taken before the repack may see the table as empty after commit, meaning careful planning is essential.
PostgreSQL 19 reached GA today, according to the Databricks blog.
Create a new Lakebase project and select PostgreSQL 19 as the version.
The release adds REPACK for online space reclamation, pg_plan_advice and pg_stash_advice for query‑plan guidance, and WAIT FOR LSN for read‑your‑writes on replicas.
By embedding REPACK, plan advice, and replica read‑your‑writes directly into the core, PostgreSQL 19 shifts maintenance from a scheduled outage to an on‑demand operation. Lakebase’s same‑day availability shows how close collaboration between a cloud provider and the open‑source community can accelerate feature delivery. As enterprises adopt the new controls, the balance between reliability and operational agility may tilt decisively toward the latter.
Sources: Hacker News; Databricks Blog (https://www.databricks.com/blog/postgresql-19-available-lakebase)