<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/what-s-new-in-postgres-19-planetscale-2t7xqm2gt" -->

---
title: What's new in Postgres 19 — PlanetScale | daily.dev
description: Postgres 19 Beta 2 brings the REPACK command into core, replacing the need for pg_repack and pg_squeeze extensions when compacting bloated tables. REPACK...
canonical: https://daily.dev/posts/what-s-new-in-postgres-19-planetscale-2t7xqm2gt
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: What's new in Postgres 19 — PlanetScale | daily.dev
og:description: Postgres 19 Beta 2 brings the REPACK command into core, replacing the need for pg_repack and pg_squeeze extensions when compacting bloated tables. REPACK...
og:url: https://daily.dev/posts/what-s-new-in-postgres-19-planetscale-2t7xqm2gt
og:image: https://api.daily.dev/og/posts/2T7xqm2gT.png
og:image:alt: What's new in Postgres 19 — PlanetScale
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# What's new in Postgres 19 — PlanetScale

**[PlanetScale](https://daily.dev/sources/planetscale)** · 9 min read · 0 upvotes · 0 comments

## Summary

Postgres 19 Beta 2 brings the REPACK command into core, replacing the need for pg_repack and pg_squeeze extensions when compacting bloated tables. REPACK (CONCURRENTLY) rewrites a table online, holding only a brief exclusive lock during the final swap, though it is not MVCC-safe and has requirements around wal_level and primary keys. JIT compilation is now disabled by default because it was misfiring on OLTP queries whose cost estimates hovered near the jit_above_cost threshold. The planner also gains eager aggregation, which can pre-aggregate rows before a join, plus a faster anti-join path for NOT IN and a new pg_plan_advice feature to pin query plans. Other smaller changes include lz4 becoming the default TOAST compression, logged lock waits, faster foreign-key inserts, wider MultiXact offsets, parallel autovacuum, new SQL syntax (GROUP BY ALL, ON CONFLICT DO SELECT, temporal FOR PORTION OF), retired RADIUS auth, and property graph support. GA is expected September or October.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://planetscale.com/blog/whats-new-in-postgres-19>

## Questions this post answers

### How do I shrink a bloated Postgres table without locking it for the whole rewrite?

PostgreSQL 19 adds REPACK (CONCURRENTLY), which rewrites a table online while continuing to accept reads and writes. It takes a SHARE UPDATE EXCLUSIVE lock, snapshots the table via logical decoding, builds a new copy, replays the backlog of writes, and only takes a brief ACCESS EXCLUSIVE lock during the final file swap. It requires wal_level replica or higher and a primary key or replica identity.

_Track how Postgres 19's REPACK changes online maintenance workflows on daily.dev._

### Why is JIT compilation disabled by default in Postgres 19?

JIT is turned off by default because Postgres could not reliably predict which queries would benefit from it, causing small OLTP queries whose cost estimates crossed jit_above_cost to pay LLVM compile overhead that exceeded their actual execution time. JIT still helps genuinely long-running analytical queries, but developers now need to opt in rather than have it enabled globally as it had been since Postgres 12.

_Follow Postgres 19 configuration defaults like this on daily.dev before upgrading production databases._

### What does eager aggregation do in the Postgres 19 query planner?

Eager aggregation lets Postgres pre-aggregate rows on the many side of a join before performing the join, rather than joining everything first and aggregating afterward. For example, summing 200,000 orders by customer before joining to a 1,000-row customers table collapses the join to 1,000 rows. It is on by default but only fires when the planner expects at least an 8x row reduction, controlled by min_eager_agg_group_size.

_Compare query plan changes like eager aggregation on daily.dev when evaluating a Postgres 19 upgrade._

## Similar posts on daily.dev

- [PostgreSQL 19 Beta Introduces SQL Graph Queries and Concurrent Table Repacking](https://daily.dev/posts/postgresql-19-beta-introduces-sql-graph-queries-and-concurrent-table-repacking-2adopzbmz) · InfoQ · 90 upvotes · 4 comments
- [Waiting for PostgreSQL 19 – Introduce the REPACK command – select \* from depesz;](https://daily.dev/posts/waiting-for-postgresql-19-introduce-the-repack-command-select-from-depesz--naffqzlbk) · depesz · 27 upvotes · 0 comments

---

Tags: [#postgresql](https://daily.dev/tags/postgresql), [#compiler-optimization](https://daily.dev/tags/compiler-optimization)

[View this post on daily.dev](https://daily.dev/posts/what-s-new-in-postgres-19-planetscale-2t7xqm2gt)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"What's new in Postgres 19 — PlanetScale","url":"https://daily.dev/posts/what-s-new-in-postgres-19-planetscale-2t7xqm2gt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/what-s-new-in-postgres-19-planetscale-2t7xqm2gt"},"datePublished":"2026-09-10T14:53:18.098Z","dateModified":"2026-09-15T01:23:39.869Z","description":"Postgres 19 Beta 2 brings the REPACK command into core, replacing the need for pg_repack and pg_squeeze extensions when compacting bloated tables. REPACK...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d29d0c7970e2f147d580ed220802cb42?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d29d0c7970e2f147d580ed220802cb42?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"PlanetScale","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"PlanetScale","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/09515c29cafc45618b3f117eab4fccf8","url":"https://daily.dev/squads/planetscale"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/what-s-new-in-postgres-19-planetscale-2t7xqm2gt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"postgresql,compiler-optimization","timeRequired":"PT9M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"PlanetScale","item":"https://daily.dev/squads/planetscale"},{"@type":"ListItem","position":3,"name":"What's new in Postgres 19 — PlanetScale"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/what-s-new-in-postgres-19-planetscale-2t7xqm2gt#faq","mainEntity":[{"@type":"Question","name":"How do I shrink a bloated Postgres table without locking it for the whole rewrite?","acceptedAnswer":{"@type":"Answer","text":"PostgreSQL 19 adds REPACK (CONCURRENTLY), which rewrites a table online while continuing to accept reads and writes. It takes a SHARE UPDATE EXCLUSIVE lock, snapshots the table via logical decoding, builds a new copy, replays the backlog of writes, and only takes a brief ACCESS EXCLUSIVE lock during the final file swap. It requires wal_level replica or higher and a primary key or replica identity. Track how Postgres 19's REPACK changes online maintenance workflows on daily.dev."}},{"@type":"Question","name":"Why is JIT compilation disabled by default in Postgres 19?","acceptedAnswer":{"@type":"Answer","text":"JIT is turned off by default because Postgres could not reliably predict which queries would benefit from it, causing small OLTP queries whose cost estimates crossed jit_above_cost to pay LLVM compile overhead that exceeded their actual execution time. JIT still helps genuinely long-running analytical queries, but developers now need to opt in rather than have it enabled globally as it had been since Postgres 12. Follow Postgres 19 configuration defaults like this on daily.dev before upgrading production databases."}},{"@type":"Question","name":"What does eager aggregation do in the Postgres 19 query planner?","acceptedAnswer":{"@type":"Answer","text":"Eager aggregation lets Postgres pre-aggregate rows on the many side of a join before performing the join, rather than joining everything first and aggregating afterward. For example, summing 200,000 orders by customer before joining to a 1,000-row customers table collapses the join to 1,000 rows. It is on by default but only fires when the planner expects at least an 8x row reduction, controlled by min_eager_agg_group_size. Compare query plan changes like eager aggregation on daily.dev when evaluating a Postgres 19 upgrade."}}]}
```

