Postgres at Any Scale
summary
Claims practical steps: start with pg_dump backups and tested restores, use wal-e for continuous WAL archiving to S3, add not‑null/unique/index/check/enum/range/jsonb constraints and an exclusion constraint to prevent billing overlaps, and use the uuid→bytea trick for exclusion indexes. For scale, run hot standbys and mix synchronous writes, or install the open‑source Citus Postgres extension to shard and distribute queries — authors report 500–700× speedups on some queries and ~500k writes/sec on a 32‑node cluster (7M in bulk inserts).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:09Overview
- 1:39Data Size
- 2:31Backups
- 4:33Constraints
- 9:15Columns
- 11:40Data types as constraints
- 13:28Range data types
- 15:45enums
- 17:34medium
- 28:01architecture
- 33:15questions
related talks
36mPostgres at any Scale
30mManaging Postgres at scale: Challenges, Tools & Techniques
51mScaling Postgres to the next level at OpenAI
58mScaling Postgres
48mHow to Tame A Mastodon: Lessons for PostgreSQL at Scale
25mData-intensive PostgreSQL: Three ways to scale
46mHow we made PG Fitter, Happier, More Productive
43mTuning PostgreSQL for High Write Workloads