Configure a minimum connection pool size
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 8.7k
- Forks
- 374
- Avg merge
- 11d 16h
- Merged PRs (30d)
- 1
Description
Is it possible to configure the postgres client to maintain a minimum connection pool size?
Creating connections is an expensive process, I'm looking to ensure a minimum baseline of connections to mitigate latency as the pool warms up to it's max
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
No files or tests are named. Start by tracing the postgres client's existing connection-pool configuration and max handling, then determine how pool warm-up is currently exercised. Done means a configured minimum baseline can be maintained while the requested maximum behavior remains clear and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs, postgres
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100