Update > Guide > Database Upgrade > Cleanup steps #368
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
Preview Available 🚀Commit Author: Matty Stratton Preview Link: turbot-com-git-docs-guardrailsupdate-guide-databa-18ac89-turbot.vercel.app |
… guide and ensure caution message formatting is consistent.
Preview Available 🚀Commit Author: Matty Stratton Preview Link: turbot-com-git-docs-guardrailsupdate-guide-databa-18ac89-turbot.vercel.app |
There was a problem hiding this comment.
Pull Request Overview
This PR augments the Database Upgrade guide by refining the resource cleanup instructions after a successful switchover and adding a new section for cleaning up replication artifacts if an upgrade fails or is aborted.
- Clarified deletion steps for the new TED stack and associated AWS resources post-upgrade
- Introduced a "In Case of Upgrade Failure or Aborted Migration" section with SQL commands to drop publications, subscriptions, and replication slots
- Listed additional AWS resources to remove after a failed upgrade attempt
Comments suppressed due to low confidence (1)
docs/guides/hosting-guardrails/disaster-recovery/database-upgrade/index.md:553
- The SQL command for dropping a replication slot is incorrect. Use
SELECT pg_drop_replication_slot('rs_blue');instead ofSELECT * FROM ....
SELECT * FROM pg_drop_replication_slot('rs_blue');
rajlearner17
added a commit
that referenced
this pull request
Aug 18, 2025
…database upgrade guide and ensure caution message formatting is consistent.(#368) Co-authored-by: raj <raj@turbot.com>
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.
This update enhances the Database Upgrade guide by adding a cleanup section under Step 17.
The new section provides clear instructions for removing replication artifacts from the source database in the event that the upgrade fails or is manually aborted.
This ensures no residual replication configurations or resources are left behind, allowing for a clean environment for future upgrade attempts.