How Routing Reads to Replicas Took Our Primary From 90% CPU to 20%

For most of a year, every query our application made — reads and writes alike — went to the same primary Postgres instance. It worked fine until it didn't: our primary was sitting at a sustained 85-90