Hack to fix db restore with custom pg_dump format

This commit is contained in:
Ben Partridge
2019-11-12 01:15:12 +00:00
committed by root
parent f82e4e483b
commit 3e1feaa8e1

View File

@@ -68,7 +68,8 @@
overwrite: different
bucket: "{{ atl_backup_manifest.artifacts.db.location.location | urlsplit('hostname') }}"
object: "{{ atl_backup_manifest.artifacts.db.location.location | urlsplit('path') }}"
dest: "{{ atl_backup_db_dest }}"
# We write it as tar because that will force the postgresql_db module to use pg_dump rather than psql
dest: "{{ atl_backup_db_dest }}.tar"
- name: Fetch Home backup from S3
aws_s3:
@@ -96,7 +97,9 @@
template: "{{ atl_jdbc_template }}"
# Depends on fetch_backup roles
state: restore
target: "{{ atl_backup_db_dest }}"
target: "{{ atl_backup_db_dest }}.tar"
# Overwrite the dump format to be psql custom
target_opts: "-Fc"
when: db_created.changed and atl_backup_db_dest is defined