Skip to content
New issue

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

chore: prevents to bootstrapping a new cluster with a non-empty object store #83

Merged
merged 2 commits into from May 10, 2022

Conversation

sxd
Copy link
Member

@sxd sxd commented May 2, 2022

The idea behind this patch it's to prevent any cluster bootstrapping
if case the target Object Store it's already used by another backup
or it's not empty at all, thus, we can prevent the overwrite of
clusters backups and misunderstanding in the PostgreSQL timeline
when trying to recover a pod.

Closes #61

Signed-off-by: Jonathan Gonzalez V jonathan.gonzalez@enterprisedb.com

@sxd
Copy link
Member Author

sxd commented May 2, 2022

/test

@cnpg-bot
Copy link

cnpg-bot commented May 2, 2022

@sxd, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/2259718438

@jlong49 jlong49 force-pushed the dev/cnpg-61 branch 3 times, most recently from 0ea4dc3 to b4b4508 Compare May 9, 2022 19:08
sxd and others added 2 commits May 10, 2022 15:30
…t store

The idea behind this patch it's to prevent any cluster boostrapping
if case the target ObjectStore it's already used by another backup
or it's not empty at all, thuse, we can prevent the overwrite of
clusters backups and misunderstanding in the PostgreSQL timeline
when trying to recover a pod.

Closes #61

Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com>
@mnencia mnencia merged commit 7a81315 into main May 10, 2022
@mnencia mnencia deleted the dev/cnpg-61 branch May 10, 2022 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make sure the backup object store is empty when bootstrapping a new cluster
5 participants