support for separate filesystem for pg_wal and table spaces

[vipkam]

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.

[Foxeronie]

We want to create databases for customers with ~1GB of data storage. Since there are also the wal files in the data volume, we cannot guarantee this and have to claim more space based on the generated wal files.

I tried to mount an additional persistent volume to the pod, but then it can't initialize, because the data folder is not empty.

I would love to see a possibility to seperate wal files too.

[sebastianvoss]

I'm also interested in this feature to be able to use PVs on different storage class for cold storage.

@bwrobc I saw you worked on such feature in https://github.com/zalando/postgres-operator/issues/625. Are there any chances to get it merged?

[bwrobc]

"Worked on" is giving me a lot of credit, I just forward-ported an old PR #1003. You can see in my comment there a number of issues with the feature as-is, I imagine they would all need to be addressed before it was considered for merging. Merging would be the decision of the code owners, of which I am not one.

My focus at the moment is on things other than Postgres on K8s, so I can't see myself working on this for the time being.