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 2B58C539F2 for ; Fri, 1 Apr 2005 15:30:20 +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 44535-09 for ; Fri, 1 Apr 2005 14:30:18 +0000 (GMT) Received: from mail.deg.cc (mail.deg.cc [64.139.134.201]) by svr1.postgresql.org (Postfix) with ESMTP id C188453A8C for ; Fri, 1 Apr 2005 15:30:16 +0100 (BST) Received: from deg.cc (unknown [205.242.255.66]) by mail.deg.cc (Postfix) with ESMTP id 9BACF55F85; Fri, 1 Apr 2005 09:30:17 -0500 (EST) Message-ID: <424D5AFA.5090800@deg.cc> Date: Fri, 01 Apr 2005 09:30:18 -0500 From: Pallav Kalva User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040308 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Simon Riggs Cc: Jason DiCioccio , pgsql-admin@postgresql.org Subject: Re: Online Backups with 8.0 -- Confused References: <89bc2a0405033115412175ce96@mail.gmail.com> <1112315398.16721.562.camel@localhost.localdomain> In-Reply-To: <1112315398.16721.562.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200504/11 X-Sequence-Number: 17024 Simon Riggs wrote: >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. > If postgres is trying to read an archive log file which was not yet generated, why cant it read from the transaction log ? I mean the current last transaction log before you start the restoration process, wouldnt that work ? I tried restore couple of time on postgres 8 it didnt give me this error, can anyone tell me how to reproduce this error, we are planning to move to 8.0 soon and I will be using online backups . > >Best Regards, Simon Riggs > > >---------------------------(end of broadcast)--------------------------- >TIP 7: don't forget to increase your free space map settings > > >