report.
           </para></listitem>
          </varlistentry>

          <varlistentry>
           <term>Int64</term>
           <listitem><para>
            The number of bytes from the current tablespace for which
            processing has been completed.
           </para></listitem>
          </varlistentry>
         </variablelist>
        </listitem>
       </varlistentry>
      </variablelist>

      <para>
       After the CopyOutResponse, or all such responses, have been sent, a
       final ordinary result set will be sent, containing the WAL end position
       of the backup, in the same format as the start position.
      </para>

      <para>
       The tar archive for the data directory and each tablespace will contain
       all files in the directories, regardless of whether they are
       <productname>PostgreSQL</productname> files or other files added to the same
       directory. The only excluded files are:

       <itemizedlist spacing="compact" mark="bullet">
        <listitem>
         <para>
          <filename>postmaster.pid</filename>
         </para>
        </listitem>
        <listitem>
         <para>
          <filename>postmaster.opts</filename>
         </para>
        </listitem>
        <listitem>
         <para>
          <filename>pg_internal.init</filename> (found in multiple directories)
         </para>
        </listitem>
        <listitem>
         <para>
          Various temporary files and directories created during the operation
          of the PostgreSQL server, such as any file or directory beginning
          with <filename>pgsql_tmp</filename> and temporary relations.
         </para>
        </listitem>
        <listitem>
         <para>
          Unlogged relations, except for the init fork which is required to
          recreate the (empty) unlogged relation on recovery.
         </para>
        </listitem>
        <listitem>
         <para>
          <filename>pg_wal</filename>, including subdirectories. If the backup is run
          with WAL files included, a synthesized version of <filename>pg_wal</filename> will be
          included, but it will only contain the files necessary for the
          backup to work, not the rest of the contents.
         </para>
        </listitem>
        <listitem>
         <para>
          <filename>pg_dynshmem</filename>, <filename>pg_notify</filename>,
          <filename>pg_replslot</filename>, <filename>pg_serial</filename>,
          <filename>pg_snapshots</filename>, <filename>pg_stat_tmp</filename>, and
          <filename>pg_subtrans</filename> are copied as empty directories (even if
          they are symbolic links).
         </para>
        </listitem>
        <listitem>
         <para>
          Files other than regular files and directories, such as symbolic
          links (other than for the directories listed above) and special
          device and operating system files, are skipped.  (Symbolic links
          in <filename>pg_tblspc</filename> are maintained.)
         </para>
        </listitem>
       </itemizedlist>
       Owner, group, and file mode are set if the underlying file system on
       the server supports it.
      </para>
     </listitem>
    </varlistentry>
   </variablelist>
  </para>

  <para>
   In all the above commands,
   when specifying a parameter of type <type>boolean</type> the
   <replaceable class="parameter">value</replaceable> part can be omitted,
   which is equivalent to specifying <literal>TRUE</literal>.
  </para>
 </sect1>

<sect1 id="protocol-logical-replication">
 <title>Logical Streaming Replication Protocol</title>

 <para>
  This section describes the logical replication protocol, which is the message
  flow started by the <literal>START_REPLICATION</literal>
  <literal>SLOT</literal> <replaceable class="parameter">slot_name</replaceable>
  <literal>LOGICAL</literal> replication command.
 </para>

 <para>
  The logical streaming replication protocol builds on the primitives