kubegres: Backup failed
We enabled the backup function as documented here and get the following error.
28/08/2021 00:00:01 - Starting DB backup of Kubegres resource postgres into file: /var/lib/backup/postgres-backup-28_08_2021_00_00_01.gz
28/08/2021 00:00:01 - Running: pg_dumpall -h postgres-replica -U postgres -c | gzip > /var/lib/backup/postgres-backup-28_08_2021_00_00_01.gz
pg_dump: error: Dumping the contents of table "table" failed: PQgetResult() failed.
pg_dump: error: Error message from server: ERROR: canceling statement due to conflict with recovery
DETAIL: User query might have needed to see row versions that must be removed.
pg_dump: error: The command was: COPY public.table(column1, column2) TO stdout;
pg_dumpall: error: pg_dump failed on database "db", exiting
28/08/2021 00:00:01 - DB backup completed for Kubegres resource postgres into file: /var/lib/backup/postgres-backup-28_08_2021_00_00_01.gz
In this Stackoverflow post they recommend that we should activate hot_standby_feedback or increase max_standby.
Is there a suggested solution from your side to overcome this issue?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 25 (14 by maintainers)
Commits related to this issue
- #36 : Fixed issue where when a kubernetes YAML field 'spec.customConfig' is updated, the code did not check whether the new custom ConfigMap had backup script. If it does not have it, the fix makes su... — committed to reactive-tech/kubegres by alex-arica 3 years ago
- #36 #40 : Updated version to 1.12 in kubegres.yaml — committed to reactive-tech/kubegres by alex-arica 3 years ago
Thank you so much for your help!
I am able to reproduce it by following the same order than you in the creation process. I am working on a fix. Most likely it would be ready tomorrow.
We have a customized Image of our kubegres-controller because of Issue #27 . I would prefer to wait until the shm feature is implemented and then update.