aboutsummaryrefslogtreecommitdiffhomepage
path: root/tasks/postgres-standby-basebackup.yml
diff options
context:
space:
mode:
authorPaul B <paul@bonaud.fr>2020-05-28 18:41:49 +0200
committerPaul B <paul@bonaud.fr>2020-06-05 14:37:21 +0200
commitb722248ed7c4a7aba2b047855b983d72a9725209 (patch)
treec76ddecb3b0434e45f481e8b0585e3b62ae31bb0 /tasks/postgres-standby-basebackup.yml
parent9e6f9658fbf5db657a2dd8465bf0ae4f41da161e (diff)
downloadansible-postgresql-role-b722248ed7c4a7aba2b047855b983d72a9725209.tar.gz
ansible-postgresql-role-b722248ed7c4a7aba2b047855b983d72a9725209.tar.zst
ansible-postgresql-role-b722248ed7c4a7aba2b047855b983d72a9725209.zip
standby-clone: Allow cloning of standby server with pg_basebackup
Right now the role assumes you have a base backup available with Barman. However if you don't have an initial barman backup you might want to clone the primary server directly to setup your standby server. This PR adds a new `primary.pg_basebackup` option to the cluster configuration which if enabled (set to `true`) will create a `/root/standby-clone-{{ postgres_version }}-{{ postgres_cluster_name }}.sh` script on the standby server which helps to initialise a standby server. ⚠️ Breaking change: the current role behavior which creates a cloning script fetching the initial backup from barman will not be enabled by default anymore. You will need to add the new `primary.restore_barman_directory` option in your role configuration to do so. ⚠️
Diffstat (limited to 'tasks/postgres-standby-basebackup.yml')
-rw-r--r--tasks/postgres-standby-basebackup.yml4
1 files changed, 4 insertions, 0 deletions
diff --git a/tasks/postgres-standby-basebackup.yml b/tasks/postgres-standby-basebackup.yml
new file mode 100644
index 0000000..db52d55
--- /dev/null
+++ b/tasks/postgres-standby-basebackup.yml
@@ -0,0 +1,4 @@
1---
2- name: Copy secondary pg_basebackup clone script
3 template: src=standby-pg_basebackup-clone.sh.j2 dest=/root/standby-clone-{{ postgres_version }}-{{ postgres_cluster_name }}.sh mode=0755
4 no_log: true