archive_command was duplicated in backup.sgml

From: Noboru Saito <noborusai(at)gmail(dot)com>
To: Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: archive_command was duplicated in backup.sgml
Date: 2023-01-14 01:00:26
Message-ID: CAAM3qnKYit5c_r+o5wYXZ7vZT3=pmJAU2uJmBGiBX=ffncDBMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hi,
<varname>archive_command</varname> was written twice in backup.sgml.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 8bab521718..be05a33205 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -956,8 +956,7 @@ SELECT * FROM pg_backup_stop(wait_for_archive => true);
On a standby, <varname>archive_mode</varname> must be
<literal>always</literal> in order
for <function>pg_backup_stop</function> to wait.
Archiving of these files happens automatically since you have
- already configured <varname>archive_command</varname> or
<varname>archive_library</varname> or
- <varname>archive_command</varname>.
+ already configured <varname>archive_command</varname> or
<varname>archive_library</varname>.
In most cases this happens quickly, but you are advised to monitor your
archive system to ensure there are no delays.
If the archive process has fallen behind because of failures of the

Attachment Content-Type Size
backup_archive_command_duplicated.patch text/x-patch 903 bytes

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Noboru Saito 2023-01-14 22:24:55 Re: archive_command was duplicated in backup.sgml
Previous Message Corey Huinker 2023-01-13 22:07:17 Adding visual clues that accesskey exists