zalando / zalando/postgres-operator
Server connection is getting crashed when connection pooler is enabled and connection pool mode is set as "session"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hi Team
we are facing issue with the postgress db connection when connected through connection pooler with "session'" mode
Where are db connection are getting crashed and showing error in connection pooler "server conn crashed " and query is not executing.
we have increased the db max connections to 100 and the default pool size to 25
Even though after increasing the connections we are facing same error with the connection pooler.
Please help us to resolve the issue.
Operator version - 1.8.2
Contributor guide
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 failure with operator version 1.8.2, a PostgreSQL connection pooler in session mode, and the reported connection settings. Inspect the pooler and operator logs around the “server conn crashed” error; done means queries execute successfully without the connection being dropped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100