the history of the server, the server will stream all the WAL on that

timeline starting from the requested start point up to the point where

the server switched to another timeline. If the client requests

streaming at exactly the end of an old timeline, the serverresponds

immediately with CommandComplete without entering COPYmode.

streaming at exactly the end of an old timeline, the serverskips COPY

mode entirely.

</para>

<para>

</para>

<para>

When the backup is started, the server will first send two

ordinary result sets, followed by one or moreCopyResponse

ordinary result sets, followed by one or moreCopyOutResponse

results.

</para>

<para>

</variablelist>

</para>

<para>

After the second regular result set, one or moreCopyResponse results

After the second regular result set, one or moreCopyOutResponse results

will be sent, one for the main data directory and one for each additional tablespace other

than <literal>pg_default</literal> and <literal>pg_global</literal>. The data in

theCopyResponse results will be a tar format (following the

theCopyOutResponse results will be a tar format (following the

<quote>ustar interchange format</quote> specified in the POSIX 1003.1-2008

standard) dump of the tablespace contents, except that the two trailing

blocks of zeroes specified in the standard are omitted.

After the tar data is complete, and if a backup manifest was requested,

anotherCopyResponse result is sent, containing the manifest data for the

anotherCopyOutResponse result is sent, containing the manifest data for the

current base backup. In any case, a final ordinary result set will be

sent, containing the WAL end position of the backup, in the same format as

the start position.