backup.sgml typo - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject backup.sgml typo
Date
Msg-id 20230114.110234.666053507266410467.t-ishii@sranhm.sra.co.jp
Whole thread Raw
Responses Re: backup.sgml typo
List pgsql-hackers
There seem to be a small typo in backup.sgml
(<varname>archive_command</varname> is unnecessarily
repeated). Attached is a patch to fix that.

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
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

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: postgres_fdw uninterruptible during connection establishment / ProcSignalBarrier
Next
From: Andres Freund
Date:
Subject: Re: Decoupling antiwraparound autovacuum from special rules around auto cancellation