MeltanoLabs / MeltanoLabs/target-postgres
Tests are failing with FATAL: sorry, too many clients already
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 23
- Avg merge
- 4h 45m
- Merged PRs (30d)
- 4
Description
Hi @visch, @BuzzCutNorman, and @edgarrmondragon,
it looks like this one is tripping again. I am observing it on my workstation, and on CI, like at GH-250. Do you think that would qualify to re-open this ticket?
@visch said:
Verified that this opens up 100 connections in my use case. This seems like multiple issues.
- Pooling doesn't seem to be working properly / setup properly
That would also be my personal feeling about the situation. However, I haven't been able to take a closer look up until now, and thought it would be a good idea to talk to you beforehand.
With kind regards,
Andreas.
Originally posted by @amotl in https://github.com/MeltanoLabs/target-postgres/issues/124#issuecomment-1862969053
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 reproducing the failing tests or CI behavior described here and compare it with GH-250. Investigate the PostgreSQL connection pooling setup and determine whether it opens excessive connections; done means the tests and CI no longer fail with “too many clients already.”
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100