The Reason For Reversions | Scaling Postgres 437

In this episode of Scaling Postgres, we discuss the reasons for all the PG 19 reversions, why open source wins, the cost of REPACK CONCURRENTLY and hint implementations.

Content Discussed

• Are we reverting patches because of bugs found by AI?
• Why open source always wins
• What REPACK (CONCURRENTLY) costs while it runs
• Postgres REPACK
• Query Plan Hints in PostgreSQL 19: A New Postgres Feature You Will Probably Never Need
• A Hint of Dependence
• GSoC B-Tree Merge
• ALTER FUNCTION SET work_mem: Fixing PostgreSQL Disk Spills Without a Global Change
• PgQ and PgQue: Workflow Engines you might need in PostgreSQL
• Row-level security performance in PostgreSQL, measured
• PgBouncer and RLS: tenant context, SET LOCAL, shared plans
• PostgresEDI September 2026 Meetup Recap: tiering to Iceberg, and Postgres from Nuxt
• pg_clickhouse & chdb updates: Encoding, nesting, and types
• PostgreSQL indexes for multi-tenant SaaS: tenant_id first
• Invoice numbers per tenant in PostgreSQL, without gaps
• What a 4 TiB Azure Disk Taught Us about Slow Reads
• How to Inspect a pg_dump Without Restoring It
• Let's Get Down to Business with Rails and PostgreSQL
• Our Interleaved Backfill Wrote Three Times the WAL
• Contributions for week 38
• What Development Looked Like at PGConf.dev 2026
• Scalefield v1.30.0: Meet the platform, and what's new
• How we systematically improved our reliability
• Handling hot shards
• When to choose x86-64 vs aarch64
• AWS and AMD bring 5th generation AMD EPYC processors to Amazon Aurora and Amazon RDS
• Resolving PostgreSQL replication lag with heartbeat tables in change data capture scenarios
• How to stream PostgreSQL changes to Amazon S3 with AWS Fargate

YouTube Video

Podcast Audio