of the backup. The backup may be stored either in the "plain" or the "tar"

format; this includes tar-format backups compressed with any algorithm

supported by <application>pg_basebackup</application>. However, at present,

<literal>WAL</literal> verification is supported only for plain-format

backups. Therefore, if the backup is stored in tar-format, the

<literal>-n, --no-parse-wal</literal> option should be used.

<varlistentry>

<term><option>-F <replaceable class="parameter">format</replaceable></option></term>

<term><option>--format=<replaceable class="parameter">format</replaceable></option></term>

<listitem>

<para>

Specifies the format of the backup. <replaceable>format</replaceable>

can be one of the following:

<variablelist>

<varlistentry>

<term><literal>p</literal></term>

<term><literal>plain</literal></term>

<listitem>

<para>

Backup consists of plain files with the same layout as the

source server's data directory and tablespaces.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><literal>t</literal></term>

<term><literal>tar</literal></term>

<listitem>

<para>

Backup consists of tar files, which may be compressed. A valid

backup includes the main data directory in a file named

<filename>base.tar</filename>, the WAL files in

<filename>pg_wal.tar</filename>, and separate tar files for

each tablespace, named after the tablespace's OID. If the backup

is compressed, the relevant compression extension is added to the

end of each file name.

</para>

</listitem>

</varlistentry>

</variablelist></para>

</listitem>

</varlistentry>

override CPPFLAGS := -I$(libpq_srcdir) $(CPPFLAGS)

astreamer_verify.o \