v0.2.22

This is QA pre-release per request #970
We will cut a release when the QA cycle will be finished.

v0.2.21

This is QA pre-release to test changes in background WAL upload

v0.2.20

This is QA pre-release intended to test libsodium settings.
#776

v0.2.19

Notable changes in this release include:

1. Fixes for S3 and GCP storages #656 #756.
2. Add wal-show command to get information about wal storage folder.
3. Add wal-verify command. It checks the integrity of WAL history starting from the oldest backup available in current timeline history.
4. Add wal-receive command. You can use WAL-G as a replica running on another host to ensure RPO=0. This is beta functionality: API may change in the future.
5. Add reverse delta unpack for backup-fetch (--reverse-unpack flag).
6. Add redundant archives skipping for backup-fetch (--skip-redundant-tars flag, designed to work in pair with reverse delta unpack).
7. Add page checksum verification for backup-push (--verify flag).

You can find more about some of these new features in Daniil Zakhlystov's post

v0.2.18

This is QA prerelease to test new wal-receive feature.

v0.2.17

This is QA pre-release to cope with AWS S3 SDK bug. See wal-g/storages#22, #656 and #727 for details.

v0.2.16

This is a QA pre-release to test refined logic of parallel WAL upload.
See #644 for details.

v0.2.15

Notable changes in this release include:

• Support of Libsodium encryption
• Retryer for AWS storage
• Go modules
• Add catchup commands. It allows cut replication lag on a PostgreSQL cluster.
  Simple scenario:

1. Get current LSN of a replica with high replication lag.
2. Create an incremental backup with catchup-push since the replica LSN.
3. Apply it to the replica with catchup-fetch command.

Thanks for all your contributions, bug reports, and feature requests!

v0.2.14a

Draft prerelease to test #593

v0.2.14

In this pre-release:

1. Fix prefetch for LZO archives. Bug #472 was greatly reducing the parallelism of WAL-E archive restoration.
2. Support SCRAM-SHA-256 authentication (actually, just PGX upgrade)
3. Fix support of 9.4 (we tried to check system identifier in a way that is not compatible with 9.4)