diff --git a/doc/pgprobackup.xml b/doc/pgprobackup.xml
index 88ce237d5..a394cbcd4 100644
--- a/doc/pgprobackup.xml
+++ b/doc/pgprobackup.xml
@@ -1875,8 +1875,9 @@ pg_probackup restore -B backup_dir --instance DROP DATABASE command.
- If want to decouple a single cluster with multiple databases into separate clusters with minimal downtime, then
- you can partially restore cluster as standby via options.
+ To decouple a single cluster containing multiple databases into separate clusters with minimal downtime,
+ you can do partial restore of the cluster as a standby using the option
+ for specific databases.
@@ -1886,10 +1887,12 @@ pg_probackup restore -B backup_dir --instance
- Due to how recovery works in PostgreSQL versions lower than 12 it is advisable to
- disable option, when running partial
- restore of PostgreSQL cluster of version less than .
- Otherwise recovery may fail.
+ Due to recovery specifics of PostgreSQL versions earlier than 12,
+ it is advisable that you set the
+ hot_standby
+ parameter to off when running partial
+ restore of a PostgreSQL cluster of version earlier than 12.
+ Otherwise the recovery may fail.
@@ -3976,10 +3979,11 @@ pg_probackup restore -B backup_dir --instance PostgreSQL cluster from a corrupt or an invalid backup.
Use with caution.
- When used with incremental restore this flag
- allows to replace already existing PGDATA with different system ID. In case of tablespaces,
- remapped via --tablespace-mapping option into non-empty directories,
- the content of such directories will be deleted.
+ If PGDATA contains a non-empty directory with system ID different from that
+ of the backup being restored, incremental restore
+ with this flag overwrites the directory contents (while an error occurs without the flag). If tablespaces
+ are remapped through the --tablespace-mapping option into non-empty directories,
+ the contents of such directories will be deleted.
@@ -4425,7 +4429,7 @@ pg_probackup archive-get -B backup_dir --instance
Specifies the timestamp up to which recovery will proceed.
- If timezone offset is not specified, local timezone is used.
+ If the time zone offset is not specified, the local time zone is used.
Example: --recovery-target-time='2020-01-01 00:00:00+03'
@@ -4615,7 +4619,7 @@ pg_probackup archive-get -B backup_dir --instance
Specifies the timestamp up to which the backup will stay
pinned. Must be an ISO-8601 complaint timestamp.
- If timezone offset is not specified, local timezone is used.
+ If the time zone offset is not specified, the local time zone is used.
Example: --expire-time='2020-01-01 00:00:00+03'pFad - Phonifier reborn
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.