Releases: wal-g/wal-g
v0.2.5
v0.2.4
This pre-release fixes WAL-E backup-fetch.
In previous pre-releases, during the introduction of Storage Folder abstraction, we misplaced check of dedicated pg_control tar. This check was performed before we knew that backup is done via WAL-E and has no separate pg_control tar.
v0.2.3
v0.2.2
v0.2.1
This is an experimental version with a major refactoring of the storage logic.
This refactoring allowed to include support of Google Cloud Storage and file system for storage platform.
lz4 codec is updated to fix lz4 issues of v0.2.0.
Also, @savichev-igor restructured files structure and build logic to make it easier to dive in for future contributors.
v0.2.0
v0.1.15
Severe WAL delete error fixed.
Due to incorrect WAL window computation, WAL retention window could be much narrower than oldest backups. LATEST backup would still recovery correctly (including PITR), but older backups could miss necessary WALs for recovery.
The issue was introduced in v0.1.13 (2018-10-27) with commit 8791dfe , version v0.1.12 is not affected.
In future releases delete tests will be covered by integration e2e test, this release includes only unit tests.
Also, this release includes some minor error formatting enhancements.
v0.1.13
v0.1.12
Fixes:
- Zstd is temporarily disabled due to corruption reports. We have reproduction and working on fixing the issue. The issue arises on delta backups with a base larger than few Tb on highly concurrent uploads. More info can be found here and here.
- Fixed WAL prefetch. WALs close to the end of the current timeline were downloaded without parallelism.
Features:
- Backup-fetch now retries failed tars with decreasing concurrency to mitigate issues of S3 implementations with throttling on the server side.
- WAL-G now has end-to-end integration tests in docker.
News:
- Considering Brotli as alternative codec with good CPU vs compression ratio tradeoff.
- Forked branch REL0_1_STABLE to separate development and support.
Stay tuned.