Skip to content

Commit ab3c6d4

Browse files
committed
doc: document how the backup manifest is transferred
Reported-by: Bernd Helmle Discussion: https://postgr.es/m/31acf8b0f1f701d53245e0cae38abdf5c3a0d559.camel@oopsware.de Backpatch-through: 13
1 parent 953c64e commit ab3c6d4

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

doc/src/sgml/protocol.sgml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2666,8 +2666,10 @@ The commands accepted in replication mode are:
26662666
<quote>ustar interchange format</quote> specified in the POSIX 1003.1-2008
26672667
standard) dump of the tablespace contents, except that the two trailing
26682668
blocks of zeroes specified in the standard are omitted.
2669-
After the tar data is complete, a final ordinary result set will be sent,
2670-
containing the WAL end position of the backup, in the same format as
2669+
After the tar data is complete, and if a backup manifest was requested,
2670+
another CopyResponse result is sent, containing the manifest data for the
2671+
current base backup. In any case, a final ordinary result set will be
2672+
sent, containing the WAL end position of the backup, in the same format as
26712673
the start position.
26722674
</para>
26732675

0 commit comments

Comments
 (0)