zalando / zalando/postgres-operator
implementing pgpool as optional connection pooler (like pgbouncer)
Open
Nobody has claimed this yet.
discussion
idea
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Hello
I would like to implement support for pgpool, much like there is for pgbouncer.
Is there any work done in that direction ?
Would it be a good idea ?
How one should go about doing it from the current code base ?
Thanks
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
The issue names existing pgbouncer support but no files, tests, or entry points. Start by locating that support in the postgres-operator codebase and determine how an optional pgpool integration would fit. The work is not ready to start until its scope and acceptance criteria are clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100