Connect-Timeout Behavior - Include Waiting for Connection Pool
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.7k
- Forks
- 374
- Avg merge
- 11d 16h
- Merged PRs (30d)
- 1
Description
We need our data-access code to be within a timeout. Currently, it seems the connect-timeout setting and behavior doesn't account for the time it takes for a connection to be avilable in the pool. Meaning, when the pool is exhausted, waiting for a connection when making a query can take longer than the connect-timeout setting.
This causes our system to spiral out of control since we have automated request timeouts and retries. We don't want to increase the connection pool in this case and we prefer to fail the requests, and use the connect-timeout for that.
To summarize, we need a connection-timeout behavior that accounts for waiting for the pool to have a connection available. Do you have any guidance as to how we can achieve it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by tracing the connect-timeout handling and the connection-pool acquisition path in the Postgres.js codebase. Done means the configured timeout includes time spent waiting for an available pooled connection, with regression coverage for an exhausted pool.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs, postgresql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100