<term><option>-i</option></term>

<term><option>--interactive</option></term>

Issues a verification prompt before doing anything destructive.

<term><option>-f</option></term>

<term><option>--force</option></term>

Attempt to terminate all existing connections to the target database

before dropping it. See <xref linkend="sql-dropdatabase"/> for more

information on this option.

<term><option>--no-slot</option></term>

This option prevents the creation of a temporary replication slot

during the backup even if it's supported by the server.

Temporary replication slots are created by default if no slot name

is given with the option <option>-S</option> when using log streaming.

The main purpose of this option is to allow taking a base backup when

the server is out of free replication slots. Using replication slots

is almost always preferred, because it prevents needed WAL from being

removed by the server during the backup.

<term><option>--no-verify-checksums</option></term>

Disables verification of checksums, if they are enabled on the server

the base backup is taken from.

</para>

<para>

By default, checksums are verified and checksum failures will result

in a non-zero exit status. However, the base backup will not be

removed in such a case, as if the <option>--no-clean</option> option

had been used. Checksum verifications failures will also be reported

in the <link linkend="monitoring-pg-stat-database-view">

<structname>pg_stat_database</structname></link> view.

<term><option>--manifest-force-encode</option></term>

Forces all filenames in the backup manifest to be hex-encoded.

If this option is not specified, only non-UTF8 filenames are

hex-encoded. This option is mostly intended to test that tools which

read a backup manifest file properly handle this case.

<term><option>--manifest-checksums=<replaceable class="parameter">algorithm</replaceable></option></term>

Specifies the checksum algorithm that should be applied to each file

included in the backup manifest. Currently, the available

algorithms are <literal>NONE</literal>, <literal>CRC32C</literal>,

<literal>SHA224</literal>, <literal>SHA256</literal>,

<literal>SHA384</literal>, and <literal>SHA512</literal>.

The default is <literal>CRC32C</literal>.

</para>

<para>

If <literal>NONE</literal> is selected, the backup manifest will

not contain any checksums. Otherwise, it will contain a checksum

of each file in the backup using the specified algorithm. In addition,

the manifest will always contain a <literal>SHA256</literal>

checksum of its own contents. The <literal>SHA</literal> algorithms

are significantly more CPU-intensive than <literal>CRC32C</literal>,

so selecting one of them may increase the time required to complete

the backup.

</para>

<para>

Using a SHA hash function provides a cryptographically secure digest

of each file for users who wish to verify that the backup has not been

tampered with, while the CRC32C algorithm provides a checksum which is

much faster to calculate and good at catching errors due to accidental

changes but is not resistant to targeted modifications. Note that, to

be useful against an adversary who has access to the backup, the backup

manifest would need to be stored securely elsewhere or otherwise

verified not to have been modified since the backup was taken.

<xref linkend="app-pgverifybackup" /> can be used to check the

integrity of a backup against the backup manifest.

<varlistentry>

<term><option>--extra-float-digits=<replaceable class="parameter">ndigits</replaceable></option></term>

<listitem>

<para>

Use the specified value of extra_float_digits when dumping

floating-point data, instead of the maximum available precision.

Routine dumps made for backup purposes should not use this option.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><option>--no-ensure-shutdown</option></term>

<listitem>

<para>

<application>pg_rewind</application> requires that the target server

is cleanly shut down before rewinding. By default, if the target server

is not shut down cleanly, <application>pg_rewind</application> starts

the target server in single-user mode to complete crash recovery first,

and stops it.

By passing this option, <application>pg_rewind</application> skips

this and errors out immediately if the server is not cleanly shut

down. Users are expected to handle the situation themselves in that

case.

</para>

</listitem>

</varlistentry>

<term><option>--partitions=<replaceable>NUM</replaceable></option></term>

<replaceable>NUM</replaceable> partitions of nearly equal size for

the scaled number of accounts.

Default is <literal>0</literal>, meaning no partitioning.

<term><option>--partition-method=<replaceable>NAME</replaceable></option></term>

<replaceable>NAME</replaceable> method.

Expected values are <literal>range</literal> or <literal>hash</literal>.

This option requires that <option>--partitions</option> is set to non-zero.

If unspecified, default is <literal>range</literal>.

<varlistentry>

<term><option>--show-script</option><replaceable>scriptname</replaceable></term>

<listitem>

<para>

Show the actual code of builtin script <replaceable>scriptname</replaceable>

on stderr, and exit immediately.

</para>

</listitem>

</varlistentry>

<term><option>--random-seed=</option><replaceable>SEED</replaceable></term>

Values for <replaceable>SEED</replaceable> may be:

Any value allowed for <replaceable>SEED</replaceable> may also be