A Postgres guide told startups to normalize their schema first. HN said monitoring should come before that (hatchet.run)
Hatchet's Postgres guide walks startups through schema design, query optimization, and scaling, with real thresholds — sequential scans get costly past 20k rows, autovacuum runs over an hour mean tuning is overdue.
A commenter who'd run Postgres at an early-stage startup pushed back: monitoring deserved to rank above schema design, because failure modes like transaction ID wraparound give almost no warning — and the AWS alert email is easy to miss, especially on Boxing Day.
Sign in to save