If you've ever had an application that needed hundreds (or thousands) (or tens of thousands) of connections to postgres, then you've probably needed a connection pooler. And if you've ever used PgBouncer as your connection pooler, you may have run into some challenges, or problems, or confusing behaviors, or all of the above. With knowledge of what can go wrong combined with the right monitoring, you can keep your database, clients, and DBAs happy.
In this talk, we will cover:
- Relevant configuration options and why they matter
- What to monitor both from your database and connection pooler, to improve your observability of both
- Running multiple PgBouncer processes - how to recognize the signs that you need to do this, and how to do it
