Hatchet · The startup's Postgres survival guide
hatchet.run · 2,903 words · saved by 1 readers
A guide to preventing Postgres from toppling over.
Alexander BelangerCo-FounderHatchet Over the past half year or so, I’ve been writing an internal doc for our engineers trying to distill two years of Postgres battles into a somewhat cohesive document. While I love the Postgres manual, I find it’s hard to turn to when shit hits the fan because it’s just so darn comprehensive. I thought this might be useful for others and would appreciate feedback (or other tidbits that you’ve learned running Postgres in production). Before starting Hatchet, while I was familiar with SQL, the extent of my knowledge was basically: if a query is slow, you…
saved by
related reading
- Nine ways to shoot yourself in the foot with PostgreSQLphilbooth.me
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- Making Postgres 42,000x slower because I am unemployedbyteofdev.com
- Schedule | POSETTE: An Event for Postgres 2024 - Citus Datacitusdata.com
- Blog — PlanetScaleplanetscale.com
- Databases are Fucking Stupid | Probably Danceprobablydance.com
- Explaining The Postgres Memeavestura.dev
- The only scalable delete in Postgres is DROP TABLE — PlanetScaleplanetscale.com
- Making 768 servers look like 1 — PlanetScaleplanetscale.com
- Some indexing best practices - pgMustardpgmustard.com
- Benchmarking How Workflow Execution Scales on Postgres | DBOSdbos.dev
- The lifecycle of a sharded Postgres query — PlanetScaleplanetscale.com