Set connection pool size based on database server parameters and replica count
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 74
- Forks
- 23
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 7
Description
The npgsql connection pool size is currently hard-coded, but should be a function of the max_connections database server parameter and the number of Tyger replicas.
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
Start by locating the hard-coded Npgsql connection-pool configuration in the Go repository and determine how the database server's max_connections value and Tyger replica count are available. Clarify the sizing formula and expected behavior before changing it; done means the pool size is derived from both parameters rather than a fixed value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100