On 2020/04/14 2:40, Robert Haas wrote:
On Fri, Mar 27, 2020 at 4:32 PM Andres Freund <and...@anarazel.de> wrote:
I don't like having a file format that's intended to be used by external
tools too that's undocumented except for code that assembles it in a
piecemeal fashion.  Do you mean in a follow-on patch this release, or
later? I don't have a problem with the former.

Here is a patch for that.

While reading the document that you pushed, I thought that it's better
to define index term for backup manifest, so that we can easily reach
this document from the index page. Thought? Patch attached.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
diff --git a/doc/src/sgml/backup-manifest.sgml 
b/doc/src/sgml/backup-manifest.sgml
index 376aff0d6d..b9634f2706 100644
--- a/doc/src/sgml/backup-manifest.sgml
+++ b/doc/src/sgml/backup-manifest.sgml
@@ -3,6 +3,10 @@
 <chapter id="backup-manifest-format">
  <title>Backup Manifest Format</title>
 
+  <indexterm>
+   <primary>Backup Manifest</primary>
+  </indexterm>
+
   <para>
    The backup manifest generated by <xref linkend="app-pgbasebackup" /> is
    primarily intended to permit the backup to be verified using

Reply via email to