db/pg_probackup
db/pg_probackup
1
0
Fork 0
mirror of https://github.com/postgrespro/pg_probackup.git synced 2025-02-09 14:33:17 +02:00
Code Issues Releases Activity

documentation minor fix

Browse Source
This commit is contained in:
Grigory Smolkin 2020-06-23 00:16:08 +03:00
parent f5e7e335c4
commit 0445bc6e09
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/pgprobackup.xml
View File

@ -1753,7 +1753,7 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
all data files in the data directory, validate header and checksum in
every page and replace only invalid pages and those with LSN greater
than shiftpoint.
This mode offer a far greater speed up compared to CHECKSUM, but rely
This mode offers a greater speed up compared to CHECKSUM, but rely
on two conditions to be met. First,
<ulink url="https://postgrespro.com/docs/postgresql/current/runtime-config-preset.html#GUC-DATA-CHECKSUMS">
data checksums</ulink> parameter must be enabled in data directory (to avoid corruption
@ -1762,9 +1762,9 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
Second, the <replaceable>pg_control</replaceable> file must be
synched with state of data directory. This condition cannot checked
at the start of restore, so it is a user responsibility to ensure
that pg_control contain valid information. Therefore it is not
recommended to use LSN mode in any situation, where pg_control has
been tampered with:
that <replaceable>pg_control</replaceable> contain valid information.
Therefore it is not recommended to use LSN mode in any situation,
where pg_control cannot be trusted or has been tampered with:
after <replaceable>pg_resetxlog</replaceable> execution,
after restore from backup without recovery been run, etc.
</para>
@ -1797,9 +1797,9 @@ pg_probackup restore -B <replaceable>backup_dir</replaceable> --instance <replac
pg_probackup restore -B /backup --instance node -R -I lsn
INFO: Running incremental restore into nonempty directory: "/var/lib/pgsql/12/data"
INFO: Destination directory redo point 15/2E000028 on tli 16 is within reach of backup QBRIDX with Stop LSN 14/DD0000B8 on tli 15, incremental restore in 'lsn' mode is possible
INFO: Destination directory redo point 15/2E000028 on tli 16 is within reach of backup QBRIDX with Stop LSN 14/DD0000B8 on tli 15
INFO: shift LSN: 14/DD0000B8
INFO: Restoring the database from backup at 2020-06-11 15:39:08+03
INFO: Restoring the database from backup at 2020-06-11 17:40:58+03
INFO: Extracting the content of destination directory for incremental restore
INFO: Destination directory content extracted, time elapsed: 1s
INFO: Removing redundant files in destination directory