Repository navigation
[STORY-3844] feat(events): document the MySQL myhoard_error continuous backup status - #701
Merged
Merged
Conversation
…us backup status
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
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.
The continuous backup events (
database_continuousbackup_healthy/delayed/stale) now also fire for MySQL databases with PITR. The payload doesn't change. MySQL only brings a new status value:myhoard_error.statusrow of the shared type_data table now listspgbackrest_errorandwal_errorfor PostgreSQL, andmyhoard_errorfor MySQL.Tested:
jekyll buildpasses, and the renderedevents.htmlshows the new status in the 3 tables plus the MySQL example.Related PRs: