You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
"Error while establishing postgresql connection: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
KnexTimeoutError : Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Reduced test code, for example in https://npm.runkit.com/knex or if it needs real
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.
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
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: