Provide an option to compress backups for PostreSQL and MySQL #335
Conversation
This file contains 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
gleichda
force-pushed
the
compress_backup
branch
from
e15603e to
f480c8e
Compare
|
@gleichda We have a new option in the test framework to retry API activation errors which will be good to test if yoy have bandwidth. |
|
@gleichda |
bharathkkb
approved these changes
Aug 9, 2022
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 API Spec allows to compress the Backup by just adding a
.gzto a export of type SQLEdit: As API Activation was failing multiple times again during build. Increasing the waiting time for API Activation to 900s=15min which should bring up build success again