Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add note in the manual about recovery near retention policy #980

Merged
merged 1 commit into from
Aug 29, 2024
Merged

Add note in the manual about recovery near retention policy #980

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions doc/manual/43-backup-commands.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,16 @@ command.

The recovery command has several options that modify the command behavior.

> **IMPORTANT:**
> If you're unsure whether the backup you want to recover from will be
> automatically deleted by retention policies during recovery,
> mark it issuing the [keep command](#keep) using the appropriate target.
> Once the recovery process is complete and your new PostgreSQL instance
> has reached the desired recovery target, if you don’t want to
> keep the backup beyond the retention policy, you can remove `keep`
> annotation issuing the [keep command](#keep) again using the
> `--release` option.

### Remote recovery

Add the `--remote-ssh-command <COMMAND>` option to the invocation
Expand Down
Loading