Skip to content

Conversation

davidmalloncares
Copy link
Collaborator

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

  • [n/a] 🟢 Spec tests.
  • [n/a] 🟢 Acceptance tests.

Changes include test coverage?

  • Yes
  • Not needed

Have you updated the documentation?

  • Yes, I've updated the appropriate docs
  • Not needed

@davidmalloncares davidmalloncares requested review from a team as code owners February 27, 2025 14:11
@davidmalloncares
Copy link
Collaborator Author

@GSPatton not sure who needs to review this one?

@davidmalloncares davidmalloncares requested a review from a team as a code owner March 7, 2025 10:25
@davidmalloncares davidmalloncares force-pushed the PE-40691-failed-postgres-docs branch from 41d6815 to ee252d5 Compare March 7, 2025 10:34
@davidmalloncares davidmalloncares force-pushed the PE-40691-failed-postgres-docs branch from ee252d5 to ef37785 Compare March 7, 2025 10:38
Copy link

@GSPatton GSPatton left a 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:

  1. Recovery procedures are easier to identify in the docs
  2. recovery.md links to automated_recovery.md providing more clarity to users
  3. 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.

@davidmalloncares davidmalloncares merged commit c8168e9 into main Mar 7, 2025
94 of 96 checks passed
@davidmalloncares davidmalloncares deleted the PE-40691-failed-postgres-docs branch March 7, 2025 16:39
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.

3 participants