PostgreSQL is Nowhere Near Ready
summary
Argues four concrete fixes with runnable results: add UNION DISTINCT ON to avoid generating 3,877 alternate paths on a 114×41 grid (turning an exponential search into millisecond work), add loopback connections (under 10 lines of code) and an enable_maintenance_mode flag that stops issuing XIDs when ~1,000,000 remain (notes Postgres 15 loosened that to ~3,000,000), and change TOAST to store first-chunk tuple pointers to avoid repeated toast-index lookups (tests show multi-terabyte tables and a 10 million-row demo suffer millisecond lookups and ~7× slowdowns now). Decide by those specifics.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 2:10Missing syntax in PostgreSQL
- 11:09Loopback connections and maintenance mode
- 18:20TOAST performance issues
- 27:27Optimizing TOAST storage
- 36:49Security and Q&A
related talks
27mHow Do We Get Postgres to the Next Level?
50mImproving Postgres' Efficiency
35mThe PostgreSQL Twin Bill: The 7 Deadly PostgreSQL Mistakes & Review of What's New in PostgreSQL 14
23mFuture Postgres Challenges
27mPostgres Performance in 15 Minutes
56mPerformance Improvements in PostgreSQL9 2
25mPostgreSQL performance tips you have never seen before
19mPostgreSQL Challenges