From: Pallav Kalva <pkalva@deg.cc>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Jason DiCioccio <geniusj@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Online Backups with 8.0 -- Confused
Date: Fri, 01 Apr 2005 09:30:18 -0500
Message-ID: <424D5AFA.5090800@deg.cc> (raw)
In-Reply-To: <1112315398.16721.562.camel@localhost.localdomain>
References: <89bc2a0405033115412175ce96@mail.gmail.com>
<1112315398.16721.562.camel@localhost.localdomain>
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
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: pkalva@deg.cc, simon@2ndquadrant.com, geniusj@gmail.com
Subject: Re: Online Backups with 8.0 -- Confused
In-Reply-To: <424D5AFA.5090800@deg.cc>
References: <89bc2a0405033115412175ce96@mail.gmail.com> <1112315398.16721.562.camel@localhost.localdomain> <424D5AFA.5090800@deg.cc>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox