Home Explore Blog CI



postgresql

43th chunk of `doc/src/sgml/protocol.sgml`
bc4c258bf1c403a6f20e37e825ccc0221e525930c3578d2a0000000100000fa1
           mode), and for <literal>zstd</literal> an integer between
           <literal>ZSTD_minCLevel()</literal> (usually <literal>-131072</literal>)
           and <literal>ZSTD_maxCLevel()</literal> (usually <literal>22</literal>),
           (default <literal>ZSTD_CLEVEL_DEFAULT</literal> or
           <literal>3</literal>).
          </para>

          <para>
           The <literal>long</literal> keyword enables long-distance matching
           mode, for improved compression ratio, at the expense of higher memory
           use.  Long-distance mode is supported only for
           <literal>zstd</literal>.
          </para>

          <para>
           The <literal>workers</literal> keyword sets the number of threads
           that should be used for parallel compression. Parallel compression
           is supported only for <literal>zstd</literal>.
          </para>
         </listitem>
        </varlistentry>

        <varlistentry>
         <term><literal>MAX_RATE</literal> <replaceable>rate</replaceable></term>
         <listitem>
          <para>
           Limit (throttle) the maximum amount of data transferred from server
           to client per unit of time.  The expected unit is kilobytes per second.
           If this option is specified, the value must either be equal to zero
           or it must fall within the range from 32 kB through 1 GB (inclusive).
           If zero is passed or the option is not specified, no restriction is
           imposed on the transfer.
          </para>
         </listitem>
        </varlistentry>

        <varlistentry>
         <term><literal>TABLESPACE_MAP [ <replaceable class="parameter">boolean</replaceable> ]</literal></term>
         <listitem>
          <para>
           If true, include information about symbolic links present in the
           directory <filename>pg_tblspc</filename> in a file named
           <filename>tablespace_map</filename>. The tablespace map file includes
           each symbolic link name as it exists in the directory
           <filename>pg_tblspc/</filename> and the full path of that symbolic link.
           The default is false.
          </para>
         </listitem>
        </varlistentry>

        <varlistentry>
         <term><literal>VERIFY_CHECKSUMS [ <replaceable class="parameter">boolean</replaceable> ]</literal></term>
         <listitem>
          <para>
           If true, checksums are verified during a base backup if they are
           enabled. If false, this is skipped. The default is true.
          </para>
         </listitem>
        </varlistentry>

        <varlistentry>
         <term><literal>MANIFEST</literal> <replaceable>manifest_option</replaceable></term>
         <listitem>
          <para>
           When this option is specified with a value of <literal>yes</literal>
           or <literal>force-encode</literal>, a backup manifest is created
           and sent along with the backup.  The manifest is a list of every
           file present in the backup with the exception of any WAL files that
           may be included. It also stores the size, last modification time, and
           optionally a checksum for each file.
           A value of <literal>force-encode</literal> forces all filenames
           to be hex-encoded; otherwise, this type of encoding is performed only
           for files whose names are non-UTF8 octet sequences.
           <literal>force-encode</literal> is intended primarily for testing
           purposes, to be sure that clients which read the backup manifest
           can handle this case. For compatibility with previous releases,
           the default is <literal>MANIFEST 'no'</literal>.
          </para>
         </listitem>
        </varlistentry>

        <varlistentry>
         <term><literal>MANIFEST_CHECKSUMS</literal> <replaceable>checksum_algorithm</replaceable></term>
         <listitem>
          <para>
           Specifies the checksum algorithm that should be applied

Title: Base Backup Options
Summary
A list of options for customizing the base backup process, including max rate, tablespace mapping, checksum verification, manifest creation, and manifest checksums, allowing for greater control over the backup process.