zalando / zalando/postgres-operator
support for separate filesystem for pg_wal and table spaces
Open
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? registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
- **Where do you run it - AWS EKS
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
We have workloads which are write heavy hence the mount point /home/postgres/pgdata always stay 100%.
- Is there a plan to have feature which will help to create multiple mount points for pg_wal , pg_log and different tablespaces etc.
- I tried to create a hacky way creating multiple pvs and mounting them but there is lot of manual and guess operations involved and not a clean approach.
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
No files, tests, or entry points are named in the issue. Start by tracing how the operator configures PostgreSQL storage and persistent volume mounts, then define how separate mounts for pg_wal, pg_log, and tablespaces should be configured and validated without manual steps.
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