db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-07-15 01:04:37 +02:00
Code Issues Releases Activity

More flexible configuration for databases

Browse Source 
Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
This commit is contained in:
David Steele
2016-08-24 12:39:27 -04:00
parent cd6278e5af
commit d0b6f78b20
83 changed files with 7666 additions and 2542 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
lib/pgBackRest/Protocol/ThreadGroup.pm
View File

@ -19,6 +19,7 @@ use pgBackRest::Common::Log;
use pgBackRest::Common::Wait;
use pgBackRest::Config::Config;
use pgBackRest::BackupFile;
use pgBackRest::Protocol::Protocol;
use pgBackRest::RestoreFile;
####################################################################################################################################
@ -85,14 +86,14 @@ sub threadGroupThread
eval
{
# Get the protocol object
my $oProtocol = protocolGet(undef, false, $iThreadIdx + 1);
my $oProtocol = protocolGet(
$$oCommand{param}{remote_type}, $$oCommand{param}{remote_index}, {bCache => false, iProcessIdx => $iThreadIdx + 1});
# Create a file object
$oFile = new pgBackRest::File
(
optionGet(OPTION_STANZA),
optionGet(OPTION_REPO_PATH),
optionRemoteType(),
$oProtocol,
undef, undef,
$iThreadIdx + 1