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)) --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index 3ab4153..e27734a 100644 --- a/README.md +++ b/README.md @@ -49,6 +49,17 @@ postgres_clusters: # Mandatory checksums: True # Optional fsync_enabled: False # Optional archive_enabled: False # Optional + wal_level: 'logical' # Optional + max_replication_slots: 10 # Optional + barman_directory: None # Optional + # Define cluster as a standby server + primary: # Optional + host: '127.0.1.1' # Mandatory + port: 5433 # Mandatory + replication_user: 'replicator' # Mandatory + replication_password: 'SuperSecret' # Mandatory + restore_command: None # Optional + restore_barman_directory: None # Optional # List of users to be created (optional) users: - username: 'replicator' # Mandatory -- cgit v1.2.3