@@ -1875,8 +1875,9 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
18751875 <command >DROP DATABASE</command > command.
18761876 </para >
18771877 <para >
1878- If want to decouple a single cluster with multiple databases into separate clusters with minimal downtime, then
1879- you can partially restore cluster as standby via <option >--restore-as-replica</option > options.
1878+ To decouple a single cluster containing multiple databases into separate clusters with minimal downtime,
1879+ you can do partial restore of the cluster as a standby using the <option >--restore-as-replica</option > option
1880+ for specific databases.
18801881 </para >
18811882 <note >
18821883 <para >
@@ -1886,10 +1887,12 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
18861887 </note >
18871888 <note >
18881889 <para >
1889- Due to how recovery works in PostgreSQL versions lower than 12 it is advisable to
1890- disable <option >hot_standby</option > option, when running partial
1891- restore of PostgreSQL cluster of version less than <option >12</option >.
1892- Otherwise recovery may fail.
1890+ Due to recovery specifics of PostgreSQL versions earlier than 12,
1891+ it is advisable that you set the
1892+ <ulink url =" https://postgrespro.com/docs/postgresql/current/runtime-config-replication.html#GUC-HOT-STANDBY" ulink >
1893+ parameter to <literal >off</literal > when running partial
1894+ restore of a PostgreSQL cluster of version earlier than 12.
1895+ Otherwise the recovery may fail.
18931896 </para >
18941897 </note >
18951898 </refsect3 >
@@ -3976,10 +3979,11 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
39763979 this flag if you need to restore the
39773980 <productname >PostgreSQL</productname > cluster from a corrupt or an invalid backup.
39783981 Use with caution.
3979- When used with <link linkend =" pbk-incremental-restore" link > this flag
3980- allows to replace already existing PGDATA with different system ID. In case of tablespaces,
3981- remapped via <literal >--tablespace-mapping</literal > option into non-empty directories,
3982- the content of such directories will be deleted.
3982+ If <envar >PGDATA</envar > contains a non-empty directory with system ID different from that
3983+ of the backup being restored, <link linkend =" pbk-incremental-restore" link >
3984+ with this flag overwrites the directory contents (while an error occurs without the flag). If tablespaces
3985+ are remapped through the <literal >--tablespace-mapping</literal > option into non-empty directories,
3986+ the contents of such directories will be deleted.
39833987 </para >
39843988 </listitem >
39853989 </varlistentry >
@@ -4425,7 +4429,7 @@ pg_probackup archive-get -B <replaceable>backup_dir</replaceable> --instance <re
44254429 <listitem >
44264430 <para >
44274431 Specifies the timestamp up to which recovery will proceed.
4428- Iftimezone offset is not specified, localtimezone is used.
4432+ Ifthe time zone offset is not specified,the localtime zone is used.
44294433 </para >
44304434 <para >
44314435 Example: <literal >--recovery-target-time='2020-01-01 00:00:00+03'</literal >
@@ -4615,7 +4619,7 @@ pg_probackup archive-get -B <replaceable>backup_dir</replaceable> --instance <re
46154619 <para >
46164620 Specifies the timestamp up to which the backup will stay
46174621 pinned. Must be an ISO-8601 complaint timestamp.
4618- Iftimezone offset is not specified, localtimezone is used.
4622+ Ifthe time zone offset is not specified,the localtime zone is used.
46194623 </para >
46204624 <para >
46214625 Example: <literal >--expire-time='2020-01-01 00:00:00+03'</literal >