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

v1.05: Bug Fix for Tablespace Link Checking

Bug Fixes:

* Fixed an issue where tablespace paths that had $PGDATA as a substring would be identified as a subdirectories of $PGDATA even when they were not. Also hardened relative path checking a bit. (Reported by Chris Fort.)
This commit is contained in:
David Steele 2016-08-09 10:06:21 -04:00
parent 34afe5e85b
commit 9f19e13095
4 changed files with 202 additions and 203 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.04](https://github.com/pgbackrest/pgbackrest/releases/tag/release/1.04) is the current stable release. Release notes are on the [Releases](http://www.pgbackrest.org/release.html) page.
pgBackRest [v1.05](https://github.com/pgbackrest/pgbackrest/releases/tag/release/1.05) 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

@ -109,7 +109,7 @@
</contributor-list>
<release-list>
<release date="XXXX-XX-XX" version="1.05dev" title="UNDER DEVELOPMENT">
<release date="2016-08-09" version="1.05" title="Bug Fix for Tablespace Link Checking">
<release-core-list>
<release-bug-list>
<release-item>

View File

@ -27,7 +27,7 @@ use constant BACKREST_CONF => BACKREST_
# 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.05dev';
use constant BACKREST_VERSION => '1.05';
push @EXPORT, qw(BACKREST_VERSION);
# Format Format Number