zalando / zalando/postgres-operator
Allow multiple volumes (for multiple tablespaces)
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
IIUC, the postgresql CRD only allows for a single volume to be specified. I'd like to use multiple tablespaces feature in PostgreSQL for which I need multiple volume support.
Possible use cases for this:
- 'huge tables', older partitions on slower cheaper volumes. (e.g. TimescaleDB, Spilo image seems to have this extension already.)
- 'huge database size', allow to put some tables on separate volumes with different I/O requirements, or the indexes of some.
Possibly related: #479
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 postgresql CRD and the related issue #479, then compare the requested behavior with PostgreSQL's CREATE TABLESPACE documentation. The work is done when the operator accepts and manages multiple volumes so users can place tablespaces on separate storage, with the relevant behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100