Comment Comment by welder Three real-world issues I've run into recently with PgBouncer + Postgres are:1. pool exhaustion from idle connections inside open long-running transactions2. SQLAlchemy's client-side pool using dead connections that PgBouncer had already killed, causing periodic request errors3. Some tasks have to bypass PgBouncer when they use SET or prepared statementsI've already sharded large datasets at the application layer, but looks like PgDog solves the above problems for any future work? parent welder 4 months ago
1. pool exhaustion from idle connections inside open long-running transactions
2. SQLAlchemy's client-side pool using dead connections that PgBouncer had already killed, causing periodic request errors
3. Some tasks have to bypass PgBouncer when they use SET or prepared statements
I've already sharded large datasets at the application layer, but looks like PgDog solves the above problems for any future work?