Table Lock Explosion! | Scaling Postgres 391

In this episode of Scaling Postgres, we discuss the issues of partition locking during planning, the problem of too much memory, the importance of a txvector column and an upcoming sale on my course.

Content Discussed

• #PostgresMarathon 2-009: Prepared statements and partitioned table lock explosion, part 1
• #PostgresMarathon 2-010: Prepared statements and partitioned table lock explosion, part 2
• #PostgresMarathon 2-011: Prepared statements and partitioned tables — the paradox, part 3
• Don't give Postgres too much memory
• Do you really need tsvector column?
• PostgreSQL Partition Pruning: The Role of Function Volatility
• "You Don't Need Kafka, Just Use Postgres" Considered Harmful
• Producing UUIDs Version 7 disguised as Version 4 (or 8)
• Beyond Start and End: PostgreSQL Range Types
• ALTER Egos: Me, Myself, and Cursor
• PostgreSQL 18 enables data‑checksums by default
• Gapless sequences
• Seamless PostgreSQL subscriber upgrades: Preserving Logical Replication state
• PostGIS Performance: Improve Bounding Boxes with Decompose and Subdivide
• Counting Customers in PostgreSQL
• October PUG Recording
• What Are “Dirty Pages” in PostgreSQL?
• NUMA, Linux, and PostgreSQL before libnuma Support
• PgPedia Week, 2025-10-19
• PgPedia Week, 2025-10-26
• Contributions for week 44, 2025
• Major compute price reduction on Neon
• Meeting High Availability Requirements in Non-Distributed PostgreSQL Deployments

YouTube Video

Podcast Audio