How Do We Get Postgres to the Next Level?

on YouTube ↗27m

" summary

PostgreSQL needs concrete fixes: establish a dedicated performance team, push toward 100% test coverage with fault‑injection and realistic performance‑regression tests, and define compatibility via a standard test suite. Roadmap items include eliminating VACUUM (20% of respondents flagged it), online major version upgrades, bitemporal tables, in‑memory hash tables and multi‑threading. Development must modularize subsystems with versioned modules and dependency checks, improve onboarding (mailing list sees ~3,000 emails/month) and create a documentation/training team plus formal advocacy.

AI-written summary · about

" chapters (6)

1. 0:00Introduction and motivation
2. 6:33Improving code quality
3. 10:52Adding new features
4. 15:46Community and advocacy
5. 22:57Conclusion and future steps
6. 24:47Q&A on vacuum issues

" related talks

• 47mThe Next 20 YearsSimon Riggs · PostgreSQL Conference Europe 2023
• 42mPostgreSQL is Nowhere Near ReadyHannu Krosing · PGCon 2023
• 17mPostgres Over the Horizon...Peter Eisentraut · PostgreSQL Conference Europe 2024
• 31mPostgres Performance for HumansCraig Kerstiens · Ancient City Ruby 2014
• 50mHacking on Postgres: An OverviewJames Coleman · PGConf NYC 2022
• 23mFuture Postgres ChallengesBruce Momjian · PGConf NYC 2022
• 51mScaling Postgres to the next level at OpenAIBohan Zhang · PGConf.dev 2025
• 56mPerformance Improvements in PostgreSQL9 2Robert Haas · Postgres Open 2012