Postgres 19 is out: try it on Neon PostgreSQL 19 reached general availability on November 19, after the release team added a second release candidate and pushed back the original October 29 date, and Neon made the version available on its platform the same day, including on its Free plan. The release adds REPACK, which reclaims space like VACUUM FULL and can physically order rows like CLUSTER, and with CONCURRENTLY rebuilds a table while normal reads and writes continue, taking an ACCESS EXCLUSIVE lock only to apply captured changes and swap files. Neon noted operational limits: concurrent repacking requires free capacity under max_repack_replication_slots, a non-deferrable primary key or suitable replica identity, temporary disk for a copy of the table and its indexes, and fails if more than about 104 million tuples are updated or deleted during the operation. Postgres 19 just went GA https://www.postgresql.org/about/news/postgresql-19-released-3449/ , and as always https://neon.com/blog/postgres-18 , it's available on Neon the same day. You can already try it on the Neon Free plan: start a Postgres 19 project from the Neon Console by choosing version 19 when you create the project, or ask your agent to do it https://neon.com/docs/ai/neon-mcp-server : This release took a little longer Postgres 19 was first scheduled for October 29. The release team added a second release candidate, moved general availability to November 19, and pulled several large features late in the cycle more on those below . Robert Haas, a Postgres committer on our team, wrote wrote a blog post discussing why https://neon.com/blog/postgres-19-is-late-and-its-ais-fault . What's new in Postgres 19 Postgres 19 is a practical release. There is no single headline feature that changes what Postgres 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. Postgres 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. We've written hands-on guides for many of these features, linked from each section below. The full list of changes is in the Postgres 19 release notes https://www.postgresql.org/docs/19/release-19.html . REPACK Postgres uses multiversion concurrency control, so an UPDATE creates a new row version and a DELETE leaves a dead tuple behind. Routine vacuuming makes that space reusable, but it doesn't necessarily return space to the operating system or restore a useful physical row order. Over time, heavily updated tables can become bloated and poorly clustered. The usual fixes have been VACUUM FULL , CLUSTER , or external tools such as pg repack . The built-in commands work, but they take an ACCESS EXCLUSIVE lock for the whole operation, blocking normal access to the table. Postgres 19 adds REPACK , which reclaims space while normal reads and writes continue during most of the operation. For example, a chat application can rebuild its messages table while clustering rows by conversation and send time using an existing index: REPACK reclaims space like VACUUM FULL ; with USING INDEX , it also physically orders rows like CLUSTER . With CONCURRENTLY , Postgres rebuilds the table while normal reads and writes continue, capturing ongoing changes through logical decoding. It then takes an ACCESS EXCLUSIVE lock to apply any remaining captured changes and swap the new table and index files into place. This phase is typically brief but can take longer on a busy table. There are operational constraints. Concurrent repacking creates an additional replication slot for the duration of the operation, so it needs free capacity under max repack replication slots and a table with either a non-deferrable primary key or a suitable index-based replica identity. It also needs temporary disk space for a copy of the table and all its indexes, potentially plus a sort file up to the size of the table. Tables with heavy update and delete traffic face an additional limit: the current upstream Postgres 19 implementation fails if more than about 104 million tuples in the target table are updated or deleted while REPACK CONCURRENTLY is running. This counts changes made during the repack, not rows already in the table. Not every relation type is eligible. Long-running transactions can delay the final lock. Concurrent repacking is also not MVCC-safe: after it commits, transactions using snapshots taken before the repack began can see the table as empty. Physical clustering also degrades as later writes arrive. REPACK CONCURRENTLY still needs planning, but it brings into core a job that previously required more downtime or an extension. Check out our full guide Query plan advice The Postgres cost-based optimizer uses table statistics and cost estimates to choose an execution plan. Most of the time, that works well. Statistics describe individual tables well, but real datasets often contain relationships that are harder to capture. Imagine that enterprise customers make up 0.1% of customers but generate 30% of orders. Per-table statistics cannot capture that cross-table correlation. With an index on orders.customer id , the planner may estimate that each enterprise customer has only a few orders and choose a nested loop that repeatedly probes the index. If those customers actually account for 30% of orders, each lookup returns far more rows than expected, and a hash join may be more appropriate. Postgres 19 adds pg plan advice and pg stash advice for these situations: - pg plan advice describes planner decisions as advice, applies supplied advice, and reports whether it was followed. - pg stash advice stores advice by query ID and applies it automatically when a matching query is planned These components do not add cross-table statistics or replace the planner. Instead, they let you intervene when an inaccurate estimate produces a poor plan. Consider a query that counts orders from enterprise customers: Here, c is the alias for the filtered customers table. The following advice asks Postgres to place those customers on the inner side of a hash join: When Postgres can apply the advice, EXPLAIN reports feedback similar to: matched means the resulting plan complies with the advice. It does not mean the new plan is necessarily better; you still need to evaluate it against the actual workload. Unlike inline optimizer hints, plan advice lives outside the application's query text. You can inspect the current plan, test focused advice, and then stash it by query ID. On Neon, pg stash advice is preloaded and loads pg plan advice automatically. You still need to create the extension in each database before using its stash-management functions: Create a stash and associate the tested advice with the query ID reported by EXPLAIN VERBOSE . Replace