archive_command was duplicated in backup.sgml

Поиск
Список
Период
Сортировка
От Noboru Saito
Тема archive_command was duplicated in backup.sgml
Дата
Msg-id CAAM3qnKYit5c_r+o5wYXZ7vZT3=pmJAU2uJmBGiBX=ffncDBMg@mail.gmail.com
обсуждение исходный текст
Ответы Re: archive_command was duplicated in backup.sgml  (Noboru Saito <noborusai@gmail.com>)
Re: archive_command was duplicated in backup.sgml  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Список 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

Вложения

В списке pgsql-docs по дате отправления:

Предыдущее
От: Corey Huinker
Дата:
Сообщение: Adding visual clues that accesskey exists
Следующее
От: Noboru Saito
Дата:
Сообщение: Re: archive_command was duplicated in backup.sgml