You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometime we face pool filling problem. When we check db and pgbouncer side we see that the pgboucner's sv_active connection doesn' match postgres side. When we see the 80 active connection per pool (we have 3 pgbouncers it means 240 active connections on db) , we cant see these active connection on postgres side we saw 60 active connections.
You don't provide evidence there is an issue here. The statistics reflects the time you run show pools. You also didn't show the output from the other 2 PgBouncer services -- the statistic is per service -- and the pg_stat_activity output. It might be the connections were closed between show pools and pg_stat_activity.
Hi;
Sometime we face pool filling problem. When we check db and pgbouncer side we see that the pgboucner's sv_active connection doesn' match postgres side. When we see the 80 active connection per pool (we have 3 pgbouncers it means 240 active connections on db) , we cant see these active connection on postgres side we saw 60 active connections.
After a while pool sessions like that:
psql (11.17, server 1.17.0/bouncer)
pgbouncer=# show pools;
database | user | cl_active | cl_waiting | cl_cancel_req | sv_active | sv_idle | sv_used | sv_tested | sv_login | maxwait | maxwait_us | pool_mode
--------------+-------------------+-----------+------------+---------------+-----------+---------+---------+-----------+----------+---------+------------+-------------
xxdb | dba | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | session
xxdb | xxdb_test_user | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | transaction
xxdb | xxdb_user | 357 | 419 | 0 | 80 | 0 | 0 | 0 | 0 | 0 | 142343 | transaction
What could be the problem?
The text was updated successfully, but these errors were encountered: