Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 2e2d460

Browse files
committed
docs: Mention that pg_combinebackup does not verify backups.
We don't want users to think that pg_combinebackup is trying to check the validity of individual backups, because it isn't. Adjust the wording about sanity checks to make it clear that verification of individual backups is the job of pg_verifybackup, and that the checks performed by pg_combinebackup are around the relationships between the backups. Per discussion with David Steele. Discussion: http://postgr.es/m/[email protected]
1 parent d9f686a commit 2e2d460

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

doc/src/sgml/ref/pg_combinebackup.sgml

+9-5
Original file line numberDiff line numberDiff line change
@@ -45,12 +45,16 @@ PostgreSQL documentation
4545
</para>
4646

4747
<para>
48-
Although <application>pg_combinebackup</application> will attempt to verify
48+
<application>pg_combinebackup</application> will attempt to verify
4949
that the backups you specify form a legal backup chain from which a correct
50-
full backup can be reconstructed, it is not designed to help you keep track
51-
of which backups depend on which other backups. If you remove the one or
52-
more of the previous backups upon which your incremental
53-
backup relies, you will not be able to restore it.
50+
full backup can be reconstructed. However, it is not designed to help you
51+
keep track of which backups depend on which other backups. If you remove
52+
the one or more of the previous backups upon which your incremental
53+
backup relies, you will not be able to restore it. Moreover,
54+
<application>pg_combinebackup</application> only attempts to verify that the
55+
backups have the correct relationship to each other, not that each
56+
individual backup is intact; for that, use
57+
<xref linkend="app-pgverifybackup" />.
5458
</para>
5559

5660
<para>

0 commit comments

Comments
 (0)