From: Simon Riggs <simon@2ndquadrant.com>
To: Jason DiCioccio <geniusj@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Online Backups with 8.0 -- Confused
Date: Fri, 01 Apr 2005 01:29:58 +0100
Message-ID: <1112315398.16721.562.camel@localhost.localdomain> (raw)
In-Reply-To: <89bc2a0405033115412175ce96@mail.gmail.com>
References: <89bc2a0405033115412175ce96@mail.gmail.com>
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
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: simon@2ndquadrant.com, geniusj@gmail.com
Subject: Re: Online Backups with 8.0 -- Confused
In-Reply-To: <1112315398.16721.562.camel@localhost.localdomain>
References: <89bc2a0405033115412175ce96@mail.gmail.com> <1112315398.16721.562.camel@localhost.localdomain>
* 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