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 <noboru...@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
