wal-g version history

- Added DIRECT-IO Reader for PostgreSQL and new commands for GPDB/CBDB continuous recovery. - Enhanced Redis sharded backups/restores and introduced partial restore for MongoDB. - Added Alibaba Cloud OSS storage support and improved S3 client functionality. - Updated Go to 1.24, refreshed linters, and improved Prometheus exporter metrics.

## 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 * tests: remove few "sleep" by @chipitsine in https://github.com/wal-g/wal-g/pull/1883 * add unit test to /wal-g/internal/databases/greenplum/backup_push_hand… by @hairy-snake in https://github.com/wal-g/wal-g/pull/1890 * tests: follow redirects when building MariaDB image by @chipitsine in https://github.com/wal-g/wal-g/pull/1889 * Bump golangci/golangci-lint-action from 6.1.1 to 6.2.0 by @dependabot in https://github.com/wal-g/wal-g/pull/1891 * Add JournalInfo deletion logic by @noname0443 in https://github.com/wal-g/wal-g/pull/1874 * Refactor tests for postgres c

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 * Add option to disable 100 continue in s3 by @fepape-ionos in https://github.com/wal-g/wal-g/pull/1829 * pg_checksum_verification_fix by @boosterKRD in https://github.com/wal-g/wal-g/pull/1828 * fix: don't ignore libsodiumKeyPath by @fepape-ionos in https://github.com/wal-g/wal-g/pull/1832 * CI: drop ubuntu-18.04 from release pipeline by @chipitsine in https://github.com/wal-g/wal-g/pull/1825 * fix data race on accessing bool var from different goroutines by @kronwerk in https://github.com/wal-g/wal-g/pull/1835 * MongoDB: Support restore of sharded cluster with PiTR by @Apelsin234 in https://github.com/wal-g/wal-g/pull/1797 * MongoDB: don't skip error if file was deleted while make backup by @Apelsin234 in h

This is a pre-release to test new AWS SDK version #1799 ## What's Changed * sqlserver: special url for proxy health-checks by @mialinx in https://github.com/wal-g/wal-g/pull/1709 * try to switch to docker compose v2 by @chipitsine in https://github.com/wal-g/wal-g/pull/1765 * add universal backup tool by @danilkaz in https://github.com/wal-g/wal-g/pull/1689 * aof datadir clean fix by @kronwerk in https://github.com/wal-g/wal-g/pull/1767 * MySQL: Add xbstream unarchiver to wal-g by @ostinru in https://github.com/wal-g/wal-g/pull/1744 * Update README.md by @reshke in https://github.com/wal-g/wal-g/pull/1772 * Fixed working without metadata by @debebantur in https://github.com/wal-g/wal-g/pull/1773 * clean only specified files and folder from data dir by @kronwerk in https://github.com/wal-g/wal-g/pull/1776 * fix checkout on Windows by @chipitsine in https://github.com/wal-g/wal-g/pull/1777 * delete single redis backup by @Believemenot in https://github.com/wal-g/wal-g/pull/1786 * 1) add backup-info cmd for redis; 2) some refactor by @kronwerk in https://github.com/wal-g/wal-g/pull/1787 * Test postgres/generic_meta_interactor.go/SetIsPermanent by @pevel-dev in https://g

Major feature of this release is full support for OrioleDB. WAL-G supported block-level incremental backups since [v0.1.3](https://github.com/wal-g/wal-g/releases/tag/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 (https://github.com/wal-g/wal-g/pull/1675, https://github.com/wal-g/wal-g/pull/1715) and fixes assorted bugs. Thanks to all the WAL-G community :) ## What's Changed * Allow users to expose debug & pprof endpoints for

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 * Fixes for working with s3 by @debebantur in https://github.com/wal-g/wal-g/pull/1718 * add test cases for tryFindHighestTimelineID by @annetannet in https://github.com/wal-g/wal-g/pull/1720 * Migrate to docker compose v2 by @debebantur in https://github.com/wal-g/wal-g/pull/1727 * сhange redis installation in tests from pkg to repo by @kronwerk in https://github.com/wal-g/wal-g/pull/1732 * Create MockObject for storage.Object and add backup tests with gomock by @alexnik10 in https://github.com/wal-g/wal-g/pull/1731 * wal-g hangs when s3 access_id or access_secret_key contains line break by @mialinx in https://github.com/wal-g/wal-g/pull/1733 * Add tests for FindTargetByName by @RedSquid2212 in https://github.com/wal-g/wal-g/pull/1729 * Refactor mongodb and redis func tests docker images by @zykovd in https://github.com/wal-g/wal-g/pull/1735 * Fix link_libsodium.sh by @garry-t in https://github.com/wal-g/wal-g/pull/1739 * Fi

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 * Support DigitalOcean Spaces (NoSuchKey during ListFolder) by @turt2live in https://github.com/wal-g/wal-g/pull/1646 * Skip archive_command check on standby by @x4m in https://github.com/wal-g/wal-g/pull/1662 * fixes for ao check config by @debebantur in https://github.com/wal-g/wal-g/pull/1664 * Fix for GP incremental backups by @debebantur in https://github.com/wal-g/wal-g/pull/1666 * Add unit tests for internal.databases.greenplum.buildFetchCommand by @denisSurkov in https://github.com/wal-g/wal-g/pull/1661 * Catchup-send and catchup-receive commands by @x4m in https://github.com/wal-g/wal-g/pull/1652 * Collecting statistics about read/written bytes by @debebantur in https://github.com/wal-g/wal-g/pull/1670 * Add Docs for und

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

This is a pre-release to test the [aws iam roles config setting](https://github.com/wal-g/wal-g/pull/1377).