An unemployed developer reverse-engineered PostgreSQL’s performance tuning to achieve the unthinkable: making the database 42,000 times slower. Through strategic sabotage of caching, vacuuming, WAL, and I/O configurations, this experiment reveals critical insights into Postgres’ performance boundaries.