-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection timeout: pool is probably full. #6034
Comments
I have the same problem |
Can you please provide a minimal reproduction repository |
No, as I can't reproduce it consistently. Sometimes re-running |
I don't know how I can help without a minimal reproduction repository as it is probably a local setup, when it happens try to connect debug the db connections |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Knex version: 3.1.0
Database + version:
PostgreSQL 13.13 (Ubuntu 13.13-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
OS: Windows 10
Node: 16.20.2
pg: 8.11.3
Bug
Explain what kind of behaviour you are getting and how you think it should do
I'm running the back end of a web app. It should start without an error
Error message
database connection to MySQL or PostgreSQL, then single file example which initializes
needed data and demonstrates the problem.
I don't have one for now. I can create a sandbox later if needed.
configs:
I've seen the same error with Prisma, which is documented here. I wonder if something similar can be done here.
The text was updated successfully, but these errors were encountered: