zalando / zalando/postgres-operator
How can we use extension pg_logical,pg_squeeze
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Please, answer some short questions which should help us to understand your problem / question better?
- Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.6.0
- **Where do you run it - cloud or metal? Kubernetes
- Are you running Postgres Operator in production? no
- Type of issue? [ question, feature request, etc.]
Hi Team,
How can we configure and use extension pg_logical, pg_squeeze using zalando-operator. currently Preload libraries support doesn't support these extensions, please suggest a way how to achieve and configure these required changes using zalando operator.
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 reviewing the operator's preload libraries support and its PostgreSQL extension configuration for pg_logical and pg_squeeze. Determine whether these extensions can be configured through the existing operator settings; done means providing a supported configuration path or clearly documenting the limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100