aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2020-08-31 18:48:38 -0400
committerBruce Momjian <bruce@momjian.us>2020-08-31 18:48:38 -0400
commit73018f564af91b135e541b28133369c5e3de975d (patch)
tree975ed1b870f954d4874d4b32c3b418e008f2c448
parent1d3ff89ecfbbdd8bf56d4773d8f2749156eeb7c1 (diff)
downloadpostgresql-73018f564af91b135e541b28133369c5e3de975d.tar.gz
postgresql-73018f564af91b135e541b28133369c5e3de975d.zip
doc: document how the backup manifest is transferred
Reported-by: Bernd Helmle Discussion: https://postgr.es/m/31acf8b0f1f701d53245e0cae38abdf5c3a0d559.camel@oopsware.de Backpatch-through: 13
-rw-r--r--doc/src/sgml/protocol.sgml6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index b27c7eaab94..d8f2d134351 100644
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -2666,8 +2666,10 @@ The commands accepted in replication mode are:
<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, a final ordinary result set will be sent,
- containing the WAL end position of the backup, in the same format as
+ After the tar data is complete, and if a backup manifest was requested,
+ another CopyResponse 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.
</para>