CASMINST-7251 - Remove Spire PostgreSQL backup procedure from documentation #5852
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spillerc-hpe
requested review from
rustydb,
atifsyedali,
haroldlongley,
jnowicki-hpe,
mharding-hpe,
shunr-hpe,
sfkramer,
brookshire,
kkelling-hpe and
don-bahls-hpe
ndavidson-hpe
approved these changes
Mar 28, 2025
nrockershousen
approved these changes
Mar 28, 2025
rustydb
approved these changes
Mar 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The Spire PostgreSQL database backup is no longer used and the procedure should be removed from documentation.
The Spire recovery procedure now reinstalls Spire without restoring the database as doing so was found to cause problems.
Checklist
.github/CODEOWNERSwith the corresponding team in Cray-HPE.