ReconnectDelay should have more flexibility
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 48
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
It would be better if ReconnectDelay had more flexibility, for instance the ability to implement exponential backoff and/or reconnect jitter to prevent stampeding herd.
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 ReconnectDelay and reading the current reconnect flow in pgxlisten. Determine the API shape needed to support exponential backoff and reconnect jitter, then define tests for the resulting delay behavior. Done means the reconnect policy supports the requested flexibility and its behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100