MeltanoLabs / MeltanoLabs/tap-postgres
Sleep between trys of Log Based WAL
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Normally when you have a timeout loop like this you'll add in some kind of "sleep" time between trying each message read so you don't ddoss your server too hard. Maybe 500ms-1s or something
Originally posted by @visch in https://github.com/MeltanoLabs/tap-postgres/pull/249#discussion_r1357354566
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 Log Based WAL timeout loop and inspect how repeated message reads are scheduled. Confirm the intended delay from the issue discussion and verify the behavior with the relevant tests; done means retries pause without changing WAL processing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100