From eda9f0c811ba115edf47b4f81200073a41d10cc3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mart=C3=ADn=20Marqu=C3=A9s?= Date: Sat, 6 Apr 2024 19:30:23 +0200 Subject: [PATCH 1/2] Remove unneeded wording in pg_combinebackup documentation --- doc/src/sgml/ref/pg_combinebackup.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/ref/pg_combinebackup.sgml b/doc/src/sgml/ref/pg_combinebackup.sgml index 658e9a759c..19b6d159ce 100644 --- a/doc/src/sgml/ref/pg_combinebackup.sgml +++ b/doc/src/sgml/ref/pg_combinebackup.sgml @@ -37,10 +37,10 @@ PostgreSQL documentation - Specify all of the required backups on the command line from oldest to newest. + Specify all required backups on the command line from oldest to newest. That is, the first backup directory should be the path to the full backup, and the last should be the path to the final incremental backup - that you wish to restore. The reconstructed backup will be written to the + you wish to restore. The reconstructed backup will be written to the output directory specified by the option. @@ -48,7 +48,7 @@ PostgreSQL documentation Although pg_combinebackup 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 + of which backups depend on which other backups. If you remove one or more of the previous backups upon which your incremental backup relies, you will not be able to restore it. -- 2.39.3