diff options
author | Robert Haas | 2024-04-18 17:06:27 +0000 |
---|---|---|
committer | Robert Haas | 2024-04-18 17:06:27 +0000 |
commit | fbed6ebe41beb72d9b7978a414ed4e8515ed1b19 (patch) | |
tree | 3417389a80a03af1dce7f2fecad204264c69ea6a | |
parent | f22e17f76cf569a797c45268081feadc8ebd68c7 (diff) |
Remove spurious "the".
Spotted by Martin Marqués.
Discussion: http://postgr.es/m/CABeG9LvQMtsKrOkhcA_mKJu1duArw4v+smeJKurYGjPVBZFecg@mail.gmail.com
-rw-r--r-- | doc/src/sgml/ref/pg_combinebackup.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/pg_combinebackup.sgml b/doc/src/sgml/ref/pg_combinebackup.sgml index c21160a195b..def1e38ae69 100644 --- a/doc/src/sgml/ref/pg_combinebackup.sgml +++ b/doc/src/sgml/ref/pg_combinebackup.sgml @@ -49,7 +49,7 @@ PostgreSQL documentation that the backups you specify form a legal backup chain from which a correct 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 + 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 |