1
0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-03-03 14:52:21 +02:00

v1.11: Bug Fix for Asynchronous Archiving Efficiency

Bug Fixes:

* Fixed an issue where asynchronous archiving was transferring one file per execution instead of transferring files in batches. This regression was introduced in v1.09 and affected efficiency only, all WAL segments were correctly archived in asynchronous mode. (Reported by Stephen Frost.)
This commit is contained in:
David Steele 2016-11-17 09:57:59 -05:00
parent dbb9d80dab
commit 54b1a784b5
4 changed files with 300 additions and 291 deletions

View File

@ -6,7 +6,7 @@ pgBackRest aims to be a simple, reliable backup and restore system that can seam
Instead of relying on traditional backup tools like tar and rsync, pgBackRest implements all backup features internally and uses a custom protocol for communicating with remote systems. Removing reliance on tar and rsync allows for better solutions to database-specific backup challenges. The custom remote protocol allows for more flexibility and limits the types of connections that are required to perform a backup which increases security.
pgBackRest [v1.10](https://github.com/pgbackrest/pgbackrest/releases/tag/release/1.10) is the current stable release. Release notes are on the [Releases](http://www.pgbackrest.org/release.html) page.
pgBackRest [v1.11](https://github.com/pgbackrest/pgbackrest/releases/tag/release/1.11) is the current stable release. Release notes are on the [Releases](http://www.pgbackrest.org/release.html) page.
## Features

File diff suppressed because it is too large Load Diff

View File

@ -133,7 +133,7 @@
</contributor-list>
<release-list>
<release date="XXXX-XX-XX" version="1.11dev" title="UNDER DEVELOPMENT">
<release date="2016-11-17" version="1.11" title="Bug Fix for Asynchronous Archiving Efficiency">
<release-core-list>
<release-bug-list>
<release-item>

View File

@ -35,7 +35,7 @@ use constant BACKREST_BIN => abs_path(
# Defines the current version of the BackRest executable. The version number is used to track features but does not affect what
# repositories or manifests can be read - that's the job of the format number.
#-----------------------------------------------------------------------------------------------------------------------------------
use constant BACKREST_VERSION => '1.11dev';
use constant BACKREST_VERSION => '1.11';
push @EXPORT, qw(BACKREST_VERSION);
# Format Format Number