#max_connections exceeding

4 messages · Page 1 of 1 (latest)

winter crow
#

Hello,
I am currently getting this error in my deployed site, i saw logs and i found out this:
packages/psycopg/connection.py", line 748, in connect django-1 | raise last_ex.with_traceback(None) django-1 | psycopg.OperationalError: connection failed: connection to server at "143.110.241.20", port 25060 failed: FATAL: remaining connection slots are reserved for roles with the SUPERUSER attribute

I also found out that there are many database connections being created .

Does anybody got similar issues once working with postgres? I have researched and it says either to increase max_connections or establish connection pool into your database.

forest canyon
#

I've seen this a couple of times ...

#

I can't remember for sure what I did about it, but I think I ran pgadmin4 (which is handy for many other things), and manually deleted the connections

winter crow
#

I still doubt that is it a primary issue with pg connections reaching its limit, or something or some code getting stuck in my production?
I mean when i saw connections they had runtime of more than 18 hours and so.

I have reported this issue to senior eng and he said there is some code getting stuck which is being run .

I dont know, and if max_connections is issue then how can we solve it? we cant obviosuly make manually deleting connections as a solution.

Do you have any ideas?
edit: This issue raise only with database connection i am using in production. not the one i use in local.