Releases: wal-g/wal-g
v0.1.10
This release is the result of QA cycle on features of v0.1.7 and v0.1.8 prereleases:
- numerous fixes and code improvements
- better disk read parallelism
- native retries for S3 storage
Also, @Aevin1387 added support for AWS Server Side Encryption.
v0.1.9
This is a QA version to test new features of v0.1.8 with fixes:
- Fixed counting and uploading of tar parts during backup-push
- Fixed delta backup inefficiency
Thanks to all collaborators who tested previous QA release, especially to @CyberDem0n, @lehni, @gregor-rayman, @davidfetter, and @rdunklau.
v0.1.8
This is a QA version to test new features:
- -v flag to read version
- parallel read from disk to further improve the performance of backup-push
- better retries for all S3 calls
- installation of user data into JSON sentinel to connect back up with external entities
- numerous refactorings and code improvements
Also, I have reports from @CyberDem0n about inefficiencies of delta backups. I cannot reproduce this reports though.
If you are looking for the stable version, please use 0.1.7.
v0.1.7
This release fixes issue #63. This issue led to the possibility of an incorrect point of restoration when the restoration was done without "standby_mode = on". The issue was reproducible only on Amazon EBS drives and frequency of reproduction varied, thanks @bartdag for extensive help with researching this issue.
Also, this release brings features shown necessary by QA cycle on the heavily loaded clusters:
- Support of parallel
wal-push
with reading from archive_status directory (relates to #58 ) - WAL-G was failing during
backup-push
if files were disappearing during tar creation. This was fixed (relates to #65 ) - Concurrency of
wal-prefetch
was improved
Some edge-case error handling and code quality work was done by @ferhatelmas. Thanks to @benubois and @lesovsky for reporting problems and sharing their experience.