From 587f87bbf278a80b14a182146724a9ebf1fd98a2 Mon Sep 17 00:00:00 2001 From: Paul B Date: Thu, 28 May 2020 15:21:12 +0200 Subject: recovery: optional restore_command & allow custom command if needed MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Right now the role assumes you always want to use barman-wal-restore script as a restore command to recover WAL files at startup time of a standby server. This PR adds a new `primary.restore_command` option which lets you override the command to use. ⚠️ Breaking change: the PR renames the existing `primary.restore_directory` option to `primary.restore_barman_directory` ⚠️ in order to give more context to this option which will automatically use the `barman-wal-restore` script as a restore command. Finally if none of the two options specified above are specified in the `primary:` object then the `restore_command` is left commented out in the PG configuration (which is totally fine as it will try to recover WALs from the primary server directly see [documentation](https://www.postgresql.org/docs/12/warm-standby.html#STANDBY-SERVER-OPERATION)) --- test/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test') diff --git a/test/main.yml b/test/main.yml index 6a819d8..7d86f8d 100644 --- a/test/main.yml +++ b/test/main.yml @@ -91,7 +91,7 @@ primary: host: postgres_one port: 5432 - restore_directory: "{{ postgres_barman_directory }}" + restore_barman_directory: "{{ postgres_barman_directory }}" replication_user: "replicator" replication_password: "secret_repli" -- cgit v1.2.3