too many clients already, remaining slots reserved for superuser
I have a production deployment where I'm facing this issue. I ran
1. Why are there so many idle connections? I understand if there are many active connections. But why idle?
2. If there are that many idle connections, shouldn't the connection pool of postgres.js kick in as it says here (https://github.com/porsager/postgres?tab=readme-ov-file#the-connection-pool) that the previous open connection will be used? So my understanding is that the idle connections will be made active with the new queries. Why isn't that happening?
3. Will I have to manually set the
4. Along with the increasing
SELECT count(*) FROM pg_stat_activitymax_connections1. Why are there so many idle connections? I understand if there are many active connections. But why idle?
2. If there are that many idle connections, shouldn't the connection pool of postgres.js kick in as it says here (https://github.com/porsager/postgres?tab=readme-ov-file#the-connection-pool) that the previous open connection will be used? So my understanding is that the idle connections will be made active with the new queries. Why isn't that happening?
3. Will I have to manually set the
idle_timeoutmax_lifetime4. Along with the increasing
max_connectionspg_bouncerGitHub
Postgres.js - The Fastest full featured PostgreSQL client for Node.js, Deno, Bun and CloudFlare - porsager/postgres
