Skip to content

Latest commit

 

History

History
179 lines (119 loc) · 5.17 KB

RELEASES.rst

File metadata and controls

179 lines (119 loc) · 5.17 KB
Raw

Releases

v1.1.0

Release v1.1.0 is compatible with older versions, and has one noteworthy detailed behavioral change:

WAL-E now ignores backing up the directories pg_log, pg_replslot, and pg_wal, all of which could cause spurious problems in backup or restore.

Other changes include:

  • It also switches to a more modern driver for Google Storage. (Samuel Kohonen)
  • Python 3.6 is now a tested (Dr. Nic Williams)
  • A counter-productive infinite retry with expired STS tokens has been fixed (Timothée Peignier)
  • The README has been expanded (tvarsis, Daniel Farina)

v1.0.3

Release v1.0.3 adds support for Keystone v3 (Joel E. Svensson).

v1.0.2

Release v1.0.2 fixes a defect in WABS storage, the offline backup feature, and documentation.

Thanks goes to: Ayush Goyal, for fixing an infinite-retry in WABS deletion. Jamal Boukaffal for a crash fix to offline backups. Norbert Tretkowski for documentation fixes.

v1.0.1

Release v1.0.1 fixes defects in WABS and Swift storage. Both were encoding errors that resulted from Python 3 conversion.

Thanks goes to: Ayush Goyal, for the fix for WABS. Joe Healy, for the fix for Swift. Derrick Petzold fixed an old reference to Python 2 in the README.

v1.0.0

Release v1.0.0 contains the conversion WAL-E from a Python 2.7 to a Python 3.4 and Python 3.5 project. It also adds support for Google Cloud Storage (Matt Wright, Daniel Farina, Samuel Kohonen).

In addition, all WAL-E storage backends have been made optional. Thus, running pip install wal-e does not install any backends by default. One must instead write a command akin to pip install wal-e[aws]. The valid options are:

  • aws
  • azure
  • google
  • swift

Finally, there are some detailed adjustments:

  • Default parallelism for wal-push has been increased to 32.
  • 404 messages have been demoted to "INFO" rather than "WARNING" because they can happen routinely and continuously, particularly with standby_mode=on (earsdown).
  • Top-level backups in Azure no longer create a nameless "directory" (Andrew Marks).
  • WAL-E start-up log message has been suppressed in some noisy cases: wal-fetch, wal-push, wal-prefetch.
  • WABS's Content-Type header is being set correctly. Previously this header was confused with Content-Encoding (David Dever).

v0.9.2

Release v0.9.2 fixes environment variable clobbering caused by the updated statement_timeout suppression patch that can break use of wrapper scripts psql. By Kenneth Shelton.

v0.9.1

Release v0.9.1 adds support for Azure SAS Tokens (by Kenny Johansson) and fixes several bugs. It is backwards and forwards compatible with v0.9.0.

The bugs fixed are:

  • Customized .psqlrc files no longer break WAL-E (Feike Steenbergen)
  • statement_timeout suppression should work now (Anatolii Mihailenco)
  • Files unlinked during backup no longer cause a crash (Léo Cavaillé)

v0.9.0

Release v0.9.0 requires use of (and adds support for) AWS SigV4. As such, a new environment variable is required, AWS_REGION, because it is part of the signature format. This is not a backwards compatible change.

Newer S3 features are often gated behind use of SigV4, and the region eu-central-1 relies on them. Because of this change, eu-central-1 is now supported.

Secondly, compatibility has been added with new versions of the Azure SDK v1.0.

v0.8.1

Release v0.8.1 drops Python 2.6 support and has minor bug fixes from v0.8.0:

  • Python 2.6 support dropped. This is on account of the Azure driver having dropped support for it.

  • Busybox compatability

    "lzop" on busybox does not have the "--stdout" flag, instead the shorthand "-c" must be used.

    There is an investigation of backwards compatability by Manuel Alejandro de Brito Fontes at #171.

  • Delete files when there is an error in their creation. Such partial files could cause confusion for Postgres, particularly when standby_mode=off is in recovery.conf.

    Ivan Evtuhovich reported the issue, tested solutions, and wrote a proof of concept of a fix: #169

  • Avoid annoying error message "invalid facility" when stderr is set as the log target. Report and fixed by Noah Yetter.

v0.8.0

Release v0.8.0 is deemed backwards and forwards compatible with WAL-E v0.7 in terms of archival format and interface. Upgrading and downgrading require no special steps.

Changes and enhancements from the v0.7 series:

  • Addition of parallel and pipelined WAL recovery

    Enabled by default, WAL-E will now perform speculative and parallel prefetching of WAL when recovering. This is an often a significant speedup in recovering or catching up databases.

  • The S3 Server Side Encryption is always set

    Because the feature is transparent outside sending a header, this is not thought to impose any changes.

  • Support an optinally specified S3 endpoint

    This allows use of alternate S3 implementations, such as "radosgw".

  • Support an optionally specified log destination

    Configuring for emitting logs on only stderr is now supported. Also supported is customizing the syslog facility logged to.