Getting stuck about node-pg-pool HOT 6 CLOSED

Try logging the number of clients in the pool before every connection. (console.log(pool.totalCount)) If you’re using one client at a time, it should stay at 1. If you can find an action that causes it to continue increasing, you’re likely forgetting to call client.release() on that path.

from node-pg-pool.

it is undefined for all of them.

from node-pg-pool.

Are you using the most recent versions of pg and pg-pool? Try upgrading.

from node-pg-pool.

the pool was conflicting with another I used (postgraphql) that uses a older version. I noticed that and force install the latest version.

This still stuck when using kue randomly after letting it run a couple hours.

from node-pg-pool.

But now console.log(pool.totalCount) as described above shows…?

from node-pg-pool.

Found a workaround (not a solution) to this issue but I think it can be justified to be closed.

I think I just found out that I simply have to clear finished tasks (perhaps overflowing the redis instance? but heroku redis free plan can only host 3000 tasks?), making the tasks retry 50 times, and also putting stuck jobs into "inactive" queue and somehow makes the task flow better now.

from node-pg-pool.