On Mon, Apr 09, 2012 at 03:37:09PM -0300, Alvaro Herrera wrote:
>
> Excerpts from Bruce Momjian's message of lun abr 09 15:13:10 -0300 2012:
> > On Mon, Apr 09, 2012 at 10:10:34AM -0400, Robert Haas wrote:
>
> > > This complaint appears to be accurate. I think we should go ahead and
> > > remove that mention.
> >
> > Agreed; removed with the attached patch. I didn't bother keeping the
> > gzip mention because I assume there is little value to using without
> > pglesslog.
>
> I'm not sure that assumption holds. I think you're thinking of the hack
> that zeroes out the "empty" holes in the middle of data pages; those
> didn't compress well unless zeroed out before compression. This tool is
> not about that, but rather about removing redundant info from WAL files.
> It seems to me that WAL files would be as gzip-compressible regardless
> of pglesslog being applied. (Another related tool is clearxlogtail
OK, docs updated with the attached patch.
> which zeroes areas from WAL files when they are empty because of an
> early switch due to archive timeout).
Should we document that?
> The funny thing is, apparently pg_lesslog was intentionally broken by
> changing XLR_BKP_REMOVABLE to XLP_BKP_REMOVABLE (different semantics?)
> and the fixes to make it compile again look simple. It's a bit strange
> that NTT stopped maintaining the tool .. Maybe it wasn't useful anymore?
No idea.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
new file mode 100644
index bd7e42d..0180df5
*** a/doc/src/sgml/backup.sgml
--- b/doc/src/sgml/backup.sgml
*************** tar -rf /var/lib/pgsql/backup.tar /var/l
*** 1246,1251 ****
--- 1246,1262 ----
Please remember to add error handling to your backup scripts.
</para>
+ <para>
+ If archive storage size is a concern, you can use
+ <application>gzip</application> to compress the archive files:
+ <programlisting>
+ archive_command = 'gzip < %p > /var/lib/pgsql/archive/%f'
+ </programlisting>
+ You will then need to use <application>gunzip</> during recovery:
+ <programlisting>
+ restore_command = 'gunzip < /mnt/server/archivedir/%f > %p'
+ </programlisting>
+ </para>
</sect3>
<sect3 id="backup-scripts">
--
Sent via pgsql-bugs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
