Drizzle Postgres connection keeps running into this issue: remaining connection slots are reserved for non-replication superuser connections #947
Replies: 2 comments
-
Hello, @juanvilladev! I was wondering if you had already solved this issue since I myself have been struggling with it for quite some time, and it is getting more frequent right now. It seems to me that the connections to the database was already exceed the its limit. Nevertheless, I would love to listen if you have workaround for this kind of problem. |
Beta Was this translation helpful? Give feedback.
-
Depending on your DB config, Postgres imposes a hard limit on the maximum number of concurrent connections, using Drizzle for example with the |
Beta Was this translation helpful? Give feedback.
-
I have a simple Drizzle setup:
I'm using Drizzle ORM inside my NextJS application and after powering up my development environment for a long time, I eventually have all my routes that use Drizzle fail with these messages:
The portion that comes from drizzle/Postgres is "remaining connection slots are reserved for non-replication superuser connections"
Any idea why this is happening?
Beta Was this translation helpful? Give feedback.
All reactions