mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Mention that pg_combinebackup does not verify backups.

Browse Source 
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/e6f930c3-590c-47b9-b094-217bb2a3e22e@pgmasters.net
This commit is contained in:
Robert Haas 2024-04-18 09:52:19 -04:00
parent d9f686a72e
commit 2e2d4604d9
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/ref/pg_combinebackup.sgml
View File

@ -45,12 +45,16 @@ PostgreSQL documentation
</para>
<para>
Although <application>pg_combinebackup</application> will attempt to verify
<application>pg_combinebackup</application> will attempt to verify
that the backups you specify form a legal backup chain from which a correct
full backup can be reconstructed, it is not designed to help you keep track
of which backups depend on which other backups. If you remove the one or
more of the previous backups upon which your incremental
backup relies, you will not be able to restore it.
full backup can be reconstructed. However, it is not designed to help you
keep track of which backups depend on which other backups. If you remove
the one or more of the previous backups upon which your incremental
backup relies, you will not be able to restore it. Moreover,
<application>pg_combinebackup</application> only attempts to verify that the
backups have the correct relationship to each other, not that each
individual backup is intact; for that, use
<xref linkend="app-pgverifybackup" />.
</para>
<para>