[trunk] PXB-3458 : Ignore invalid innodb_undo_directory setting in --copy-back mode #1718
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
…k mode https://perconadev.atlassian.net/browse/PXB-3458 Problem ------- When backup-my.cnf is used in --copy-back mode, it sets innodb_undo_directory setting to "./". This doesn't make sense in this mode, and results in a backup restoration error. Fix --- We ignore innodb_undo_directory setting if it's set to "./" in --copy-back mode.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
https://perconadev.atlassian.net/browse/PXB-3458
Problem
When backup-my.cnf is used in --copy-back mode, it sets innodb_undo_directory setting to "./". This doesn't make sense in this mode, and results in a backup restoration error.
Fix
We ignore innodb_undo_directory setting if it's set to "./" in --copy-back mode.