Restore from repo, but not have it as back-up / wall syncing #4365
Description
Overview
I have a situation in which I want to restore a back-up from a production environment to an acceptance/testing environment, but not have back-ups of that acceptance environmen.
According to https://access.crunchydata.com/documentation/postgres-operator/latest/guides/optional-backups it possible to disable back-ups in the new version by leaving spec.backups out of your definition. But as far as I can see, I need to define spec.backups in order to define a repo to restore from.
I've tried disabling the schedule as I've described here: CrunchyData/postgres-operator-examples#318, but that doesn't keep it from attempting to sync wall segments. Digging further into it however, I think it's a feature lacking in CPK itself.
For now I've prevented it from back-up segments with a read-only S3 key, but this still causes the disk to get filled up with wall segments until the database crashes from a lack of disk space. I think I might be able to work around it using: #2531 (comment) and droping the segments, but this is probably not the way this is intended to be used.
Use Case
I need to be able to grab a copy of a production database for testing purposes, but I don't need it to have back-ups.
Desired Behavior
Be able to define a repo to restore from separate from the back-ups.
Environment
Please provide the following details:
- Platform: Kubernetes
- Platform Version: 1.32.x
- PGO Image Tag: ubi9-5.8.4-0
- Postgres Version 16
- Storage: transip-fast-storage
- Number of Postgres clusters: 1