X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A1FC6538F9 for ; Fri, 1 Apr 2005 05:46:59 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47201-04 for ; Fri, 1 Apr 2005 04:46:54 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by svr1.postgresql.org (Postfix) with ESMTP id 16F1453237 for ; Fri, 1 Apr 2005 05:46:53 +0100 (BST) Received: by wproxy.gmail.com with SMTP id 68so855470wri for ; Thu, 31 Mar 2005 20:46:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=RDST4PqlTC4hzG0HWh46nX23tg6vZT0OLH4M7OirQB0ifPyH0rDtmBwBV17hRha9Gk4ghysNnZMZjZs3kNZ2woOwpwe02AFfzCxsu9nEQuiUvft4Gp5Z/HkdrONta/CJFwJzyOisWNx8/RhIg3jKqWht43e0fclSN2Fg4fK7/Vc= Received: by 10.54.67.20 with SMTP id p20mr362404wra; Thu, 31 Mar 2005 20:46:52 -0800 (PST) Received: by 10.54.18.43 with HTTP; Thu, 31 Mar 2005 20:46:52 -0800 (PST) Message-ID: <89bc2a040503312046558f48a9@mail.gmail.com> Date: Thu, 31 Mar 2005 23:46:52 -0500 From: Jason DiCioccio Reply-To: Jason DiCioccio To: Simon Riggs Subject: Re: Online Backups with 8.0 -- Confused Cc: pgsql-admin@postgresql.org In-Reply-To: <1112315398.16721.562.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <89bc2a0405033115412175ce96@mail.gmail.com> <1112315398.16721.562.camel@localhost.localdomain> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.336 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/5 X-Sequence-Number: 17018 Simon, On Mar 31, 2005 7:29 PM, Simon Riggs wrote: > > In retrospect, there is a slight timing error between end backup and > archival of next WAL log. The first-release design for PITR didn't fully > cover lower traffic situations, so in those cases the timing error > becomes noticeable. You're not the first to observe this, though only by > about a month. > > I'm considering options for the next release, since major change seems > to be required to the basic xlog handling mechanisms. Thank you very much for the info. Given the situation then, how would you recommend doing what I'm trying to do? Or what would be a good method of doing these online backups? Would doing 1 base backup a day, keeping a couple of days worth, and backing up the archive logs as the come in be the best way? I guess I was just trying to do the base and WAL backup at the same time and all at once, which is probably not what it's designed for, as I'm not figuring out. Thanks! -JD-