File tree Expand file tree Collapse file tree 1 file changed +3
-8
lines changed Expand file tree Collapse file tree 1 file changed +3
-8
lines changed Original file line number Diff line number Diff line change @@ -89,23 +89,18 @@ Role Variables
89
89
will be backed up (this can be any format supported by rsync, e.g. `user@host:/path`). The most recent backup will be
90
90
in a subdirectory named `current`.
91
91
92
- - `postgresql_backup_rotate`: Boolean, defaults to `true`, which will cause the `current` directory to be renamed prior
93
- to creating a new backup. If set to `false`, `current` will be deleted (this is useful if you are using snapshots or
94
- some other means to archive previous backups).
95
-
96
- - `postgresql_backup_local_dir`: Filesystem path on the PostgreSQL server where backup scripts will be placed and
97
- working WALs will be written prior to a WAL archive.
92
+ - `postgresql_backup_local_dir`: Filesystem path on the PostgreSQL server where backup scripts will be placed.
98
93
99
94
- `postgresql_backup_[hour|minute]`: Controls what time the cron job will run to perform a full backup. Defaults to 1:00
100
95
AM.
101
96
102
97
- `postgresql_backup_[day|month|weekday]`: Additional cron controls for when the full backup is performed (default:
103
98
`*`).
104
99
105
- - `postgresql_backup_mail_recipient`: User or address that should receive mail from the backup scripts.
106
-
107
100
- `postgresql_backup_post_command`: Arbitrary command to run after successful completion of a scheduled backup.
108
101
102
+ Additional options pertaining to backups can be found in the [defaults file](defaults/main.yml).
103
+
109
104
Dependencies
110
105
------------
111
106
You can’t perform that action at this time.
0 commit comments