Skip to content

Releases: wal-g/wal-g

v3.0.8

21 Jan 14:19
@chipitsine chipitsine
v3.0.8
f81943e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.8 Latest
Latest

Major features of this stable release are:

  • Infrastructure & CI

    • Switched tests and workflows to ubuntu-latest due to 20.04 deprecation.
    • Updated Go version to 1.24 and refreshed linters (golangci-lint v2.0+).
    • Multiple dependency upgrades (Azure SDK, OAuth2, crypto, JWT, gRPC, pgx, compress, etc.).

  • PostgreSQL / Greenplum / Cloudberry

    • Added DIRECT-IO Reader for PostgreSQL.
    • New commands for continuous recovery in GPDB/CBDB.
    • Fixes for WAL page size, block size, checksums, and Cloudberry test stability.
    • Support for xid64 patch page layout.

  • Redis

    • Enhanced support for sharded Redis backups/restores: slots info, hostname/config parsing, validation fixes.

  • MongoDB

    • Introduced partial restore and partial oplog replay.
    • Improved metadata handling and collection in separate goroutines.
    • Dropped tests for deprecated Mongo versions.

  • MySQL

    • Added binlog-list command and reconnection to binlog server.
    • Expanded unit tests for metadata fetch/set.

  • Storage Backends

    • New implementation for Alibaba Cloud OSS with multipart upload support.
    • Fixes for S3 client headers, batch deletion, SSE-C bug, and versioning behavior.
    • Added S3_DELETE_BATCH_SIZE and none compression method.

  • Exporter & Monitoring

    • Created Prometheus exporter with improved metrics (backup size, reduced binary size, better scrape intervals).
    • Performance optimizations in WAL-G exporter.

  • Other Fixes

    • Improved error handling (e.g., corrupted WAL metadata, connection refused).
    • Added retries for restore point creation.
    • Various test workflow improvements and cleanup.

What's Changed

Read more

Contributors

bonnefoa, serprex, and 32 other contributors
Assets 170

v3.0.7

13 Apr 09:44
@chipitsine chipitsine
v3.0.7
6ea13b9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.7

Major features of this stable release are:

  • From Greenplum's perspective, the following updates are beneficial: Commit 92e3995 introduces a --force-delete flag to the delete command. This enhancement enables users to effectively remove backups, even in cases where earlier deletion attempts were unsuccessful.

  • Commit 094bcb4 for Cloudberry: Added support for recognizing 'Apache Cloudberry' in the version() command, facilitating users in working with Cloudberry from the trunk branch.

  • Commit 44e4386 enhances the supply chain, resolving issues flagged by the Trivy security scanner.

What's Changed

New Contributors

Full Changelog: v3.0.5...v3.0.7

Contributors

serprex, sundbry, and 18 other contributors
Loading

v3.0.6

10 Apr 07:57
@chipitsine chipitsine
v3.0.6
6ea13b9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.6 Pre-release
Pre-release 
Prefetched wal is expected in default directory (#1954)

* get prefetch location from config

* added some logging

* added test
Loading

v3.0.5

10 Jan 13:12
@github-actions github-actions
v3.0.5
94bf839
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.5

First stable release in 2025. Major features of this stable release are:

  • Cloudberry database support
  • MongoDB 8.0 support + restore for sharded cluster with PiTR
  • PostgreSQL - fix wal-g copy

Additionally this release contains a bunch of bugfixes and documentation updates. For MySQL we fixed regression (all versions since v3.0.0 affected) that leads to broken backups to be marked as good ones. We strongly recommend MySQL users to upgrade.

What's Changed

New Contributors

Full Changelog: v3.0.4...v3.0.5

Contributors

ostinru, VGoshev, and 14 other contributors
Loading

v3.0.4

30 Oct 17:56
@x4m x4m
v3.0.4
f20428f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.4 Pre-release
Pre-release

This is a pre-release to test new AWS SDK version #1799

What's Changed

New Contributors

Full Changelog: v3.0.3...v3.0.4

Contributors

mialinx, ostinru, and 14 other contributors
Loading

v3.0.3

08 Aug 17:50
@x4m x4m
v3.0.3
3f88f3c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.3

Major feature of this release is full support for OrioleDB.
WAL-G supported block-level incremental backups since v0.1.3, but it previously treated OrioleDB data as a collection of unknown files. Now WAL-G understands if OrioleDB is installed into cluster and makes efficient backup copies of OrioleDB data. Thanks to @homper and other Supabase engineers.

Additionally, this release includes two new Postgres commands catchup-send and catchup-receive. These commands are useful when you need to bring a lagging replica up to date without pushing a new backup to the storage. In essence, they work like pg_rewind but in reverse. Perhaps we should rename them to pg_wind. Thanks to @vbp1 for drawing my attention to the problem of current catchup implementation and architecting new design.

We've also added aof-based backups for redis (@kronwerk).

This release also mitigates several CVEs in dependencies (#1675, #1715) and fixes assorted bugs. Thanks to all the WAL-G community :)

What's Changed

New Contributors

Full Changelog: v3.0.2...v3.0.3

Contributors

ostinru, berler, and 8 other contributors
Loading

v3.0.2

09 Jul 06:32
@x4m x4m
v3.0.2
124e8e7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.2 Pre-release
Pre-release

This pre-release is intended to preview OrioleDB support.

Also it fixes some bugs, notably #1736: reading calls to S3 could be really slow due to unintended bucket listings. The bug seems to be introduced in 3.0.1 pre-release.

What's Changed

New Contributors

Full Changelog: v3.0.1...v3.0.2

Contributors

mialinx, x4m, and 10 other contributors
Loading

v3.0.1

24 May 14:14
@x4m x4m
v3.0.1
a2c015d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.1 Pre-release
Pre-release

This is a technical pre-release aimed at mitigating several CVEs in dependencies (#1675, #1715). These vulenrabilities have no known ways to be exploited against WAL-G. But these days we should keep CVE scanners calm.
Also this pre-release gives access to several features that didn't make it into 3.0.0 because were not tested enough (#1662, #1646, #1652).
As usual, handful of bugs fixed.

Thanks to everyone who contributed!

What's Changed

New Contributors

Full Changelog: v3.0.0...v3.0.1

Contributors

passcod, serprex, and 24 other contributors
Loading

v3.0.0

17 Mar 10:04
@github-actions github-actions
v3.0.0
4689e3a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v3.0.0

Hello everyone!

This is a much-anticipated release. In the future, we will strive to avoid accumulating such a large number of changes. We will code frequently, ship frequently, and release frequently!

Noteworthy Changes

  • Every database engine now benefits from failover storage. This technique can save the day if one of the storage systems goes down. However, do not forget to monitor them anyway.
  • For Postgres, we have a WAL archiving daemon available. Its primary purpose is to improve the efficiency of parallel archiving. Additionally, WAL-G supports the partial restoration of a cluster. If you have large, unnecessary tables, you can exclude them from the restoration process, the Postgres will skip over the WAL records for these tables.
  • Greenplum's PITR (Point-in-Time Recovery) is undergoing its maturation process. Partial restore is supported in a similar way to Postgres. We now have tools to verify the integrity of AO\AOCS files in storage without actually restoring backups. This technique is necessary to ensure developers can sleep well, as Greenplum backups are relatively new, and extra precautions need to be taken to ensure they are safe and reliable.
  • MongoDB backups can now benefit from binary backups, which significantly reduce the impact of backups on a running workload.
  • MySQL now supports incremental backups, also known as delta backups. However, this feature is still in beta mode and the API may change in the future.
  • Also, we now have beta support for etcd. Changes necessary for real PITR have not yet been merged into etcd, and can be found at etcd-io/etcd#17233.

Detailed changes log

Read more

Contributors

Aevin1387, serprex, and 47 other contributors
Loading

2.0.2-rc1

16 Nov 11:51
@usernamedt usernamedt
v2.0.2-rc1
2f2bfd3
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
2.0.2-rc1 Pre-release
Pre-release

This is a pre-release to test the aws iam roles config setting.

Loading