mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2025-01-30 05:39:12 +02:00
v1.26: Repository Encryption
Bug Fixes: * Fixed an issue that could cause copying large manifests to fail during restore. (Reported by Craig A. James.) * Fixed incorrect WAL offset for 32-bit architectures. (Fixed by Javier Wilson.) * Fixed an issue retrieving WAL for old database versions. After a stanza-upgrade it should still be possible to restore backups from the previous version and perform recovery with archive-get. However, archive-get only checked the most recent db version/id and failed. Also clean up some issues when the same db version/id appears multiple times in the history. (Fixed by Cynthia Shang. Reported by Clinton Adams.) * Fixed an issue with invalid backup groups being set correctly on restore. If the backup cannot map a group to a name it stores the group in the manifest as false then uses either the owner of $PGDATA to set the group during restore or failing that the group of the current user. This logic was not working correctly because the selected group was overwriting the user on restore leaving the group undefined and the user incorrectly set to the group. (Reported by Jeff McCormick.) * Fixed an issue passing parameters to remotes. When more than one db was specified the path, port, and socket path would for db1 were passed no matter which db was actually being addressed. (Reported by Uspen.) Features: * Repository encryption support. (Contributed by Cynthia Shang, David Steele.)
This commit is contained in:
parent
033dbcdc20
commit
ba6b49ecb7
@ -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.25](https://github.com/pgbackrest/pgbackrest/releases/tag/release/1.25) is the current stable release. Release notes are on the [Releases](http://www.pgbackrest.org/release.html) page.
|
||||
pgBackRest [v1.26](https://github.com/pgbackrest/pgbackrest/releases/tag/release/1.26) 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
@ -10,7 +10,7 @@
|
||||
</intro>
|
||||
|
||||
<release-list>
|
||||
<release date="XXXX-XX-XX" version="1.26dev" title="UNDER DEVELOPMENT">
|
||||
<release date="2017-11-21" version="1.26" title="Repository Encryption">
|
||||
<release-core-list>
|
||||
<release-bug-list>
|
||||
<release-item>
|
||||
|
@ -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.26dev';
|
||||
use constant BACKREST_VERSION => '1.26';
|
||||
push @EXPORT, qw(BACKREST_VERSION);
|
||||
|
||||
# Format Format Number
|
||||
|
@ -6,7 +6,7 @@ package pgBackRest::LibCAuto;
|
||||
# Library version (.999 indicates development version)
|
||||
sub libcAutoVersion
|
||||
{
|
||||
return '1.26.999';
|
||||
return '1.26';
|
||||
}
|
||||
|
||||
# Configuration option value constants
|
||||
|
Loading…
x
Reference in New Issue
Block a user