The lifecycle of a sharded Postgres query — PlanetScale
planetscale.com · 5,743 words · saved by 1 readers
Follow a SQL query through the router, across four Postgres shards, and back.
If you’ve ever used Postgres and thought, “wow, this is such a simple piece of software, I understand every part of it perfectly,” you have not yet met the query planner. Now consider sharding that database across a thousand servers. How would you serve a query? All you'd need is a system that replicates the Postgres auth system, wire protocol, and parser, plus a shard-aware distributed query planner, graceful handling of all server failure scenarios, and connection pooling that overcomes the Postgres process-per-connection architecture. Easy, right? Let's follow the journey of a Postgres…
saved by
related reading
- Making 768 servers look like 1 — PlanetScaleplanetscale.com
- Blog — PlanetScaleplanetscale.com
- Herding elephants: Lessons learned from sharding Postgres at Notionnotion.so
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- The startup's Postgres survival guidehatchet.run
- Sharding with Amazon Relational Database Service | AWS Database Blogaws.amazon.com
- Explaining The Postgres Memeavestura.dev
- Schedule | POSETTE: An Event for Postgres 2024 - Citus Datacitusdata.com
- Nine ways to shoot yourself in the foot with PostgreSQLphilbooth.me
- Benchmarking How Workflow Execution Scales on Postgres | DBOSdbos.dev
- pthorpe92.devpthorpe92.dev