From: Robert Haas Date: Wed, 1 Dec 2021 13:55:00 +0000 (-0500) Subject: Document that tar archives are now properly terminated. X-Git-Url: http://git.postgresql.org/gitweb/-?a=commitdiff_plain;h=81fca310b38e7808dff9c01a26564e8f2db10893;p=users%2Frhaas%2Fpostgres.git Document that tar archives are now properly terminated. Commit 5a1007a5088cd6ddf892f7422ea8dbaef362372f changed the server behavior, but I didn't notice that the existing behavior was documented, and therefore did not update the documentation. This commit does that. I chose to mention that the behavior has changed rather than just removing the reference to a deviation from a standard. It seemed like that might be helpful to tool authors. Discussion: http://postgr.es/m/CA+TgmoaYZbz0=Yk797aOJwkGJC-LK3iXn+wzzMx7KdwNpZhS5g@mail.gmail.com --- diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index e59216e7f2..34a7034282 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -2809,8 +2809,10 @@ The commands accepted in replication mode are: than pg_default and pg_global. The data in the CopyOutResponse results will be a tar format (following the ustar interchange format 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. + standard) dump of the tablespace contents. Prior to + PostgreSQL 15, the server omitted the two trailing + blocks of zeroes specified in the standard, but this is no longer the + case. After the tar data is complete, and if a backup manifest was requested, another CopyOutResponse result is sent, containing the manifest data for the current base backup. In any case, a final ordinary result set will be