Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 08F3E2E0052 for ; Tue, 25 Mar 2008 01:50:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 91316-09 for ; Tue, 25 Mar 2008 01:50:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from smtp180.iad.emailsrvr.com (smtp180.iad.emailsrvr.com [207.97.245.180]) by postgresql.org (Postfix) with ESMTP id A9A732E002C for ; Tue, 25 Mar 2008 01:50:31 -0300 (ADT) Received: from relay8.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay8.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id CF25A1B51E0; Tue, 25 Mar 2008 00:50:30 -0400 (EDT) Received: by relay8.relay.iad.mlsrvr.com (Authenticated sender: matthew-AT-zeut.net) with ESMTP id B9FA71B47C3; Tue, 25 Mar 2008 00:50:30 -0400 (EDT) Message-ID: <47E884A1.3010407@zeut.net> Date: Tue, 25 Mar 2008 00:50:41 -0400 From: "Matthew T. O'Connor" User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Miguel Arroz CC: Steve Poe , "pgsql-performance@postgresql.org" Subject: Re: Planning hot/live backups? References: <721b21dc0803241323u73443060w3a1912d52714549b@mail.gmail.com> <47E8128E.1060600@zeut.net> <721b21dc0803241356h78257168vba3f61d8eb92a152@mail.gmail.com> <47E82B0B.7090807@zeut.net> <570D4201-082A-4586-A0F8-4345C2B5E53F@guiamac.com> In-Reply-To: <570D4201-082A-4586-A0F8-4345C2B5E53F@guiamac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/457 X-Sequence-Number: 29411 Miguel Arroz wrote: > Going a bit off topic, but one quick question: to avoid storing GB of > WAL files that will probably take a lot of time to reload, how can the > backup be "reset"? I suspect that it's something like stopping the WAL > archiving, doing a new base backup, and restart archiving, but I've > never done it (have been using SQL dumps), so... Basically, you only need WAL logs from the last time you made a back-up of your data directory. We do nightly re-rsync of our data directory and then purge old WAL files that are no longer needed.