MeltanoLabs / MeltanoLabs/tap-postgres
Database timeouts fail the tap, even though we'd expect the pool to swap out timed out connecitons
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Tech tangents reported this here https://github.com/MeltanoLabs/tap-postgres/issues/24#issuecomment-1990736024
I think we could replicate this by turning down the replication timeout to something really low like 20 seconds and testing this locally.
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 reading the linked tap-postgres issue comment, then locate the replication-timeout and connection-pool handling in this repository. Reproduce the failure locally with the replication timeout set to about 20 seconds. Done means timed-out database connections are replaced by the pool instead of causing the tap to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100