Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id C6E7A9FBB86 for ; Wed, 14 Feb 2007 04:14:04 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 77307-05 for ; Wed, 14 Feb 2007 04:14:02 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 18B809FBB66 for ; Wed, 14 Feb 2007 04:14:01 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l1E8DtbC019450; Wed, 14 Feb 2007 03:13:55 -0500 (EST) To: Michael Monnerie cc: pgsql-admin@postgresql.org Subject: Re: online tape backup In-reply-to: <200702140819.50017@zmi.at> References: <200702091951.14100.ejortegau@cable.net.co> <200702131027.02556@zmi.at> <29978.1171380879@sss.pgh.pa.us> <200702140819.50017@zmi.at> Comments: In-reply-to Michael Monnerie message dated "Wed, 14 Feb 2007 08:19:49 +0100" Date: Wed, 14 Feb 2007 03:13:55 -0500 Message-ID: <19449.1171440835@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.06 tagged_above=0 required=5 tests=AWL, BAYES_50, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200702/193 X-Sequence-Number: 24658 Michael Monnerie writes: > On Dienstag, 13. Februar 2007 16:34 Tom Lane wrote: >> You're suffering from a fundamental misconception about the nature of >> WAL. Vacuum doesn't "shrink WAL", and neither does anything else; > Seems you didn't understand me: When I make a vacuum, and then a base > backup, I do not need to include the WAL records anymore. But when I do > a base backup and afterwards vacuum, the WAL will be huge already, also > making restore much longer. This is irrelevant, at least in a steady-state environment. If you vacuum beforehand, the WAL history for that has to be included in what you need to recover from your previous base backup; and you can't discard that data until after you take the new backup. So AFAICS it's a wash; the average time-to-recover is the same either way. Or at least, VACUUM is not any different from any other burst of activity that you might want to schedule around. regards, tom lane