mzwettler2

This feature is not available yet as far as I can see in the actual docu. Isn't it?

verify only checks for file checksums, sizes + existence in the repo. would be good to have a real dry recovery test.

@jkatz We also hit this problem as we require german locales. Is there any convenient solution meanwhile?

I am not sure if I have understood your problem correctly. But you have to set pgbackrest retention management AND schedule at least one backup to get automatic archive retention...

We have the same issue after an RHEL7 upgdate: dba@pgcluster # create extension pg_cron; ERROR: could not stat file "/usr/pgsql-9.6/share/extension/pg_cron--1.2.sql": No such file or directory Time: 3.641 ms dba@pgcluster #...

Hi @ValClarkson Sorry for being unclear. When I change (reconfigure) the whole s3 bucket to a new one it works. If I only change (reconfgure) the repo1-path within the same...

I define my S3 backup location using these CRDs: PostgresCluster.spec.backups.pgbackrest.repos[index].s3 - bucket - endpoint - region PostgresCluster.spec.backups.pgbackrest - global.repo[index]-path If I change the repo-path afterwards, the backup terminates incorrectly. I...

I would need an option to trigger the execution of a new stanza-create. Anything planned?

@tjmoore4 > you are effectively just looking for an imperative way to trigger a stanza-create using the configuration already set on the PostgresCluster spec? Yes. > Have you tried exec-ing...

@tjmoore4 Thanks for adding something to your backlog. Sorry for beeing unclear. Our customers are not allowed to use kubectl. They must trigger such an action by an annotation.