Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 9EC599FBEFD for ; Fri, 16 Feb 2007 10:32:28 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 52412-02-2 for ; Fri, 16 Feb 2007 10:32:18 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by postgresql.org (Postfix) with ESMTP id EFBA79FBE8A for ; Fri, 16 Feb 2007 10:32:23 -0400 (AST) Received: by nf-out-0910.google.com with SMTP id x4so1582624nfb for ; Fri, 16 Feb 2007 06:32:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Yvvp0lFGL/071ZpR+VFFPk6/l2MUKvylUbxPy9Ri2jJLMrBoqL3s5gf/x7GDLs5XtXuTAJfR/A1Bm10ePjFF4QFefjVyIJqOHJXtQs69M2B5hlHuBqPZKLQmTNLMArQjDO4lnKfQwoYkcfLaAYH1Z8Z+M2Xq5kq5NF74sw1lL0I= Received: by 10.49.65.19 with SMTP id s19mr2350391nfk.1171625652174; Fri, 16 Feb 2007 03:34:12 -0800 (PST) Received: by 10.49.75.11 with HTTP; Fri, 16 Feb 2007 03:34:12 -0800 (PST) Message-ID: <81961ff50702160334x411e3aeau76ca57c628e0f45e@mail.gmail.com> Date: Fri, 16 Feb 2007 06:34:12 -0500 From: "Chad Wagner" To: "Eduardo J. Ortega" Subject: Re: WAL files backup Cc: pgsql-admin@postgresql.org In-Reply-To: <200702152235.57473.ejortegau@cable.net.co> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5290_21614720.1171625652118" References: <945295.11491.qm@web55414.mail.re4.yahoo.com> <200702152235.57473.ejortegau@cable.net.co> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.046 tagged_above=0 required=5 tests=AWL, BAYES_20, HTML_30_40, HTML_MESSAGE, SPF_PASS X-Spam-Level: X-Archive-Number: 200702/232 X-Sequence-Number: 24697 ------=_Part_5290_21614720.1171625652118 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 2/15/07, Eduardo J. Ortega wrote: > > After erasing the "less than names" WAL files, we add to tar the > remaining > WAL records (0003B, 0003C and so on on the example). The more WAL files > you > have after 0003B, the more up to date DB you get after restore (since it > has > more WAL files indicating more transactions that took place after the > backup. Why bother trying to delete WAL files older than the .backup file? When PostgreSQL is in recovery mode it knows which WAL files are necessary to perform the recovery. Also, the documentation recommends excluding the pg_xlog directory when performing the base backup. Likely when it comes time to recovery the online WAL files have been archived already, so it is a risk of confusion I am sure. -- Chad http://www.postgresqlforums.com/ ------=_Part_5290_21614720.1171625652118 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 2/15/07, Eduardo J. Ortega <ejortegau@cable.net.co> wrote:
After erasing the "less than  names" WAL files, we add to tar the remaining
WAL records (0003B, 0003C  and so on on the example). The more WAL files you
have after 0003B, the more up to date DB you get after restore (since it has
more WAL files indicating more transactions that took place after the backup.

Why bother trying to delete WAL files older than the .backup file?  When PostgreSQL is in recovery mode it knows which WAL files are necessary to perform the recovery.

Also, the documentation recommends excluding the pg_xlog directory when performing the base backup.  Likely when it comes time to recovery the online WAL files have been archived already, so it is a risk of confusion I am sure.



--
Chad
http://www.postgresqlforums.com/ ------=_Part_5290_21614720.1171625652118--