Technology1 min read

Postgres 19 is out, and it's available on Neon and Databricks Lakebase

By · Published by Everything Blog

In short

The release introduces native features that address critical operational pain points, led by a built-in REPACK command for reclaiming storage and reordering physical rows. When executed with the CONCURRENTLY parameter, the utility uses logical decoding so normal reads and writes can proceed, demanding only a brief final lock to swap table and index files. However, repacking introduces notable infrastructure overhead, including requirements for duplicate disk space, a dedicated replication slot, and a valid primary key.

Key points

  • Concurrent repacks will fail if more than roughly 104 million row modifications take plac…: Concurrent repacks will fail if more than roughly 104 million row modifications take place during the active operation.
  • Teams executing concurrent maintenance must allocate sufficient temporary disk storage fo…: Teams executing concurrent maintenance must allocate sufficient temporary disk storage for duplicate tables, indexes, and possible sort files.
  • The concurrent repacking process requires a dedicated replication slot, a non-deferrable…: The concurrent repacking process requires a dedicated replication slot, a non-deferrable primary key or replica identity, and is not MVCC-safe for older snapshots.

Sources checked by our analysis pipeline: 1

Try the new features: REPACK, query plan advice, WAIT FOR LSN, and more

PostgreSQL 19 reached GA today and it's already available on Lakebase. New major versions often take weeks to reach other managed PostgreSQL services. Instead, we wanted to give access to it to our customers the same day.

Several engineers on the Lakebase team are PostgreSQL committers and contributors, and they worked on this release directly, from query plan advice to shared memory, locale handling, and release management. To try it, create a new Lakebase project and select PostgreSQL 19 as the version.

PostgreSQL 19 is a practical release. There is no single headline feature that changes what PostgreSQL is. Instead, version 19 goes after operational problems that database teams know well: bloated tables, unstable query plans, replica lag, incomplete statistics, and maintenance work that is hard to run safely in production.

The common thread is control. PostgreSQL 19 gives you more ways to step in when the defaults are not enough, without giving up the project's bias toward reliability and predictable behavior.

The full list of changes…

Technology