59a214727c
By default, spilo sets WAL_BUCKET_SCOPE_PREFIX depending on the cluster namespace, possibly to a non-empty string. However, we won't be able to clone those clusters, as the clone prefix is always set to an empty string. We could go the other way around and set both WAL_BUCKET_SCOPE_PREFIX and CLONE_WAL_BUCKET_SCOPE_PREFIX to a non-default value that depends on the cluster's namespace, but it seems that we don't need this feature for now (no conflict will occur even for clusters with the same name and different namespaces because of the SCOPE_SUFFIX) and it requires some additional testing first. |
||
|---|---|---|
| .. | ||
| cluster.go | ||
| cluster_test.go | ||
| exec.go | ||
| filesystems.go | ||
| k8sres.go | ||
| pg.go | ||
| pod.go | ||
| resources.go | ||
| sync.go | ||
| types.go | ||
| util.go | ||
| volumes.go | ||