We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
because backups are eating up our storage: CrunchyData/postgres-operator#2531
Consider migration to https://cloudnative-pg.io/
https://blog.palark.com/cloudnativepg-and-other-kubernetes-operators-for-postgresql/
The text was updated successfully, but these errors were encountered:
either increasing the backup frequency might help as in CrunchyData/postgres-operator#2531 (comment)
or setting archive_mode to off as in CrunchyData/postgres-operator#2531 (comment)
Sorry, something went wrong.
/priority backlog
Extend the PVC for psql by +2Gb and wait until the DB recovers. Then trigger a one off backup either by:
oc annotate postgrescluster db --overwrite postgres-operator.crunchydata.com/pgbackrest-backup="$(date)"
or oc create job --from=cronjob/db-repo1-full db-backup-full
oc create job --from=cronjob/db-repo1-full db-backup-full
Long term we need either
implemented some altering, see https://github.com/b4mad/racing/blob/main/manifests/env/phobos/postgresql/alerting.yaml
alertmanager will send to https://discord.com/channels/850841654327640074/1106466539273732136
No branches or pull requests
because backups are eating up our storage: CrunchyData/postgres-operator#2531
Consider migration to https://cloudnative-pg.io/
https://blog.palark.com/cloudnativepg-and-other-kubernetes-operators-for-postgresql/
The text was updated successfully, but these errors were encountered: