In my last post, lesson 3 was "your database is the bottleneck, not Go" — use pgx, size the pool deliberately. A few of you asked what "deliberately" actually means. Fair question. Here's every pgxpool setting I touch in production, what it does, and the number I actually use. No theory — just the config running behind real traffic. 1. The pool is the choke point, not your code Go will happily spin up 10,000 goroutines to serve requests. If your pool holds 20 connections, 9,...