@@ -688,16 +688,14 @@ test ! -f /mnt/server/archivedir/00000001000000A900000065 && cp pg_wal/0
688688 <para>
689689 In rare cases, <productname>PostgreSQL</productname> may attempt to
690690 re-archive a WAL file that was previously archived. For example, if the
691- system crashes before the server makes a durable record of archival success,
692- the server will attempt to archive the file again after restarting (provided
693- archiving is still enabled). When an archive library encounters a
694- pre-existing file, it may return <literal>true</literal> if the WAL file has
695- identical contents to the pre-existing archive and the pre-existing archive
696- is fully persisted to storage. Alternatively, the archive library may
697- return <literal>false</literal> anytime a pre-existing file is encountered,
698- but this will require manual action by an administrator to resolve. If a
699- pre-existing file contains different contents than the WAL file being
700- archived, the archive library <emphasis>must</emphasis> return
691+ system crashes before the server makes a durable record of archival
692+ success, the server will attempt to archive the file again after
693+ restarting (provided archiving is still enabled). When an archive library
694+ encounters a pre-existing file, it should return <literal>true</literal>
695+ if the WAL file has identical contents to the pre-existing archive and the
696+ pre-existing archive is fully persisted to storage. If a pre-existing
697+ file contains different contents than the WAL file being archived, the
698+ archive library <emphasis>must</emphasis> return
701699 <literal>false</literal>.
702700 </para>
703701