From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 13 Jan 2009 00:54:11 +0000 (+0000)
Subject: Document how pglesslog can be used to reduce the storage requirements of PITR.
X-Git-Tag: recoveryinfrav9~55
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=cdcd0d18ad5e2386a502be1442ebdbe088d61493;p=users%2Fsimon%2Fpostgres.git

Document how pglesslog can be used to reduce the storage requirements of PITR.
---

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index f04d487251..fb52b50019 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1337,6 +1337,23 @@ tar -rf /var/lib/pgsql/backup.tar /var/lib/pgsql/archive/
       WAL files are part of the same <application>tar</> file.
       Please remember to add error handling to your backup scripts.
      </para>
+
+     <para>
+      If archive storage size is a concern, use <application>pg_compresslog</>,
+      <ulink url="http://pglesslog.projects.postgresql.org"></ulink>, to
+      remove unnecessary <xref linkend="guc-full-page-writes"> and trailing
+      space from the WAL files.  You can then use
+      <application>gzip</application> to further compress the output of
+      <application>pg_compresslog</>:
+<programlisting>
+archive_command = 'pg_compresslog %p - | gzip &gt; /var/lib/pgsql/archive/%f'
+</programlisting>
+      You will then need to use <application>gunzip</> and
+      <application>pg_decompresslog</> during recovery:
+<programlisting>
+restore_command = 'gunzip &lt; /mnt/server/archivedir/%f | pg_decompresslog - %p'
+</programlisting>
+     </para>
     </sect3>
 
     <sect3 id="backup-scripts">