Multiple DB Users with pgBouncer auth_query
A practical setup for dynamic user authentication via `auth_query` instead of `userlist.txt` when running pgBouncer
Series
For backend engineers who run a single PostgreSQL cluster themselves and want the habits that keep it healthy written down. The problem is staying healthy once real traffic arrives. The order is a setup order: connection pooling first, then backups, read/write splitting, schema changes without downtime, index decisions.
5-part series
Part 1 of 5
A practical setup for dynamic user authentication via `auth_query` instead of `userlist.txt` when running pgBouncer
Part 2 of 5
pg_dump alone is not a backup. A PITR-capable, compressed, verifiable backup architecture with pgBackRest, continuous WAL archiving and restore drills.
Part 3 of 5
Before scaling up the database: moving read traffic to replicas, the traps replication lag creates, and when you actually need it
Part 4 of 5
Running migrations without causing downtime in production: backward-compatible steps, multi-phase column changes, and avoiding table locks
Part 5 of 5
A missing index slows the query; too many indexes make every write expensive. Striking the right balance by measurement, not by guesswork