switch to keypool?
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 175
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
The session pool is complicated and probably not 100% correct yet. Try switching to keypool while retaining the existing API.
Contributor guide
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
Start by inspecting the existing session pool implementation and its callers, then compare the linked keypool project with the current pooling behavior. Preserve the existing public API while evaluating the replacement, and verify that the session-pool behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, scala
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100