-
Notifications
You must be signed in to change notification settings - Fork 54
(PE-40691) document automated steps for failed postgres and adding compilers #554
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
Merged
Conversation
This file contains hidden or 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
@GSPatton not sure who needs to review this one? |
lisabrady
reviewed
Mar 6, 2025
lisabrady
reviewed
Mar 6, 2025
lisabrady
reviewed
Mar 6, 2025
lisabrady
reviewed
Mar 6, 2025
lisabrady
reviewed
Mar 6, 2025
lisabrady
reviewed
Mar 6, 2025
41d6815
to
ee252d5
Compare
ee252d5
to
ef37785
Compare
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
lisabrady
reviewed
Mar 7, 2025
GSPatton
approved these changes
Mar 7, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes look good to me. The below acceptance criteria are satisfied:
- Recovery procedures are easier to identify in the docs
- recovery.md links to automated_recovery.md providing more clarity to users
- automated_recovery.md documents how to replace a failed PE-PostgreSQL server using the new plan, and how to add/replace a compiler using the add_compiler plan.
Approving. Pending approval from the documentation team.
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.
Document automated steps for failed postgres and adding compilers
Summary
Updating the docs to outline the automated approach to recovering from a failed postgres server and also for adding compilers
Checklist
Changes include test coverage?
Have you updated the documentation?