mirror of
https://github.com/postgres/postgres.git
synced 2025-07-27 12:41:57 +03:00
Remove server support for the previous base backup protocol.
Commitcc333f3233
added a new COPY sub-protocol for taking base backups, but retained support for the previous protocol. For the same reasons articulated in the message for commit9cd28c2e5f
, remove support for the previous protocol from the server. Discussion: http://postgr.es/m/CA+TgmoazKcKUWtqVa0xZqSzbKgTH+X-aw4V7GyLD68EpDLMh8A@mail.gmail.com
This commit is contained in:
@ -2634,13 +2634,8 @@ The commands accepted in replication mode are:
|
||||
<term><literal>TARGET</literal> <replaceable>'target'</replaceable></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Tells the server where to send the backup. If not specified,
|
||||
the legacy base backup protocol will be used. Otherwise, the new
|
||||
protocol will be used, as described below.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If the target is <literal>client</literal>, the backup data is
|
||||
Tells the server where to send the backup. If the target is
|
||||
<literal>client</literal>, which is the default, the backup data is
|
||||
sent to the client. If it is <literal>server</literal>, the backup
|
||||
data is written to the server at the pathname specified by the
|
||||
<literal>TARGET_DETAIL</literal> option. If it is
|
||||
@ -2866,25 +2861,8 @@ The commands accepted in replication mode are:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
After the second regular result set, one or more CopyOutResponse results
|
||||
will be sent. If the <literal>TARGET</literal> option is not specified,
|
||||
the legacy base backup protocol will be used. In this mode,
|
||||
there will be one CopyOutResponse for the main directory, one for each
|
||||
additional tablespace other than <literal>pg_default</literal> and
|
||||
<literal>pg_global</literal>, and one for the backup manifested if
|
||||
requested. The main data directory and any additional tablespaces will
|
||||
be sent in tar format (following the <quote>ustar interchange
|
||||
format</quote> specified in the POSIX 1003.1-2008 standard), and
|
||||
the manifest will sent as a plain file. Prior to
|
||||
<literal>PostgreSQL</literal> 15, the server omitted the two trailing
|
||||
blocks of zeroes specified in the standard, but this is no longer the
|
||||
case.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
New applications should specify the <literal>TARGET</literal> option.
|
||||
When that option is used, a single CopyOutResponse will be sent, and
|
||||
the payload of each CopyData message will contain a message in one of
|
||||
After the second regular result set, a CopyOutResponse will be sent.
|
||||
The payload of each CopyData message will contain a message in one of
|
||||
the following formats:
|
||||
</para>
|
||||
|
||||
@ -2898,6 +2876,10 @@ The commands accepted in replication mode are:
|
||||
<term>Byte1('n')</term>
|
||||
<listitem><para>
|
||||
Identifes the messaage as indicating the start of a new archive.
|
||||
There will be one archive for the main data directory and one
|
||||
for each additional tablespace; each will use tar format
|
||||
(following the <quote>ustar interchange format</quote> specified
|
||||
in the POSIX 1003.1-2008 standard).
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
|
Reference in New Issue
Block a user