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 815C5537AB for ; Fri, 1 Apr 2005 01:31:33 +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 24284-06 for ; Fri, 1 Apr 2005 00:31:32 +0000 (GMT) Received: from cmailm2.svr.pol.co.uk (cmailm2.svr.pol.co.uk [195.92.193.210]) by svr1.postgresql.org (Postfix) with ESMTP id 3A7D2537A4 for ; Fri, 1 Apr 2005 01:31:31 +0100 (BST) Received: from modem-3147.lion.dialup.pol.co.uk ([217.135.172.75] helo=192.168.0.102) by cmailm2.svr.pol.co.uk with esmtp (Exim 4.41) id 1DHA4U-0006xq-7X; Fri, 01 Apr 2005 01:31:34 +0100 Subject: Re: Online Backups with 8.0 -- Confused From: Simon Riggs To: Jason DiCioccio Cc: pgsql-admin@postgresql.org In-Reply-To: <89bc2a0405033115412175ce96@mail.gmail.com> References: <89bc2a0405033115412175ce96@mail.gmail.com> Content-Type: text/plain Organization: 2nd Quadrant Date: Fri, 01 Apr 2005 01:29:58 +0100 Message-Id: <1112315398.16721.562.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.048 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/3 X-Sequence-Number: 17016 On Thu, 2005-03-31 at 18:41 -0500, Jason DiCioccio wrote: > Now, realize that ..0022 was not in the archive directory, and > actually is still not. However, it seems to be requiring it. Do I > have to wait for this log to be archived? Yes. > Is there a way that I can > force the archival of this WAL log? No, other than write lots of stuff to a table. Straight answers, but I hope that helps. 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. Best Regards, Simon Riggs