Connection limit being reached too soon
I'm having issues with connection limit.
I'm using 0.25 CU and Paid Plan. The
I'm using pgbouncer, 3 services, each service has its own username.
Sometimes I get these connections spikes of 55 connections (picture), and when this happens, no service can create more connections.
I don't get it. The connection limit should be 112, not 55.
Also, the connection limit for a misbehaving service should be 64, preventing it from exhausting connections for others.
During these high-connections times the neon UI cannot connect to Postgres, so I cannot run
I'm using 0.25 CU and Paid Plan. The
SHOW max_connections; returns 112.I'm using pgbouncer, 3 services, each service has its own username.
Sometimes I get these connections spikes of 55 connections (picture), and when this happens, no service can create more connections.
I don't get it. The connection limit should be 112, not 55.
Also, the connection limit for a misbehaving service should be 64, preventing it from exhausting connections for others.
During these high-connections times the neon UI cannot connect to Postgres, so I cannot run
select * from pg_stat_activity to debug it or so...
