Thread: archive_command was duplicated in backup.sgml

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

This has been fixed so it is closed.
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=1334b79a359fb842d2d3cfe5b61ad4ccff8b82a4

Thank you.

2023年1月14日(土) 10:00 Noboru Saito <noborusai@gmail.com>:
>
> 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

Saito-san,

Oh, I didn't realize that you have aready pointed out this 1 hour
earlier than me. Sorry for this.

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp

From: Noboru Saito <noborusai@gmail.com>
Subject: archive_command was duplicated in backup.sgml
Date: Sat, 14 Jan 2023 10:00:26 +0900
Message-ID: <CAAM3qnKYit5c_r+o5wYXZ7vZT3=pmJAU2uJmBGiBX=ffncDBMg@mail.gmail.com>

> 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