Re: Incrementally Updated Backups and restartpoints - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Incrementally Updated Backups and restartpoints
Date
Msg-id 3f0b79eb1001131413v4ccc8ac1jf25a1f75cf71d5ce@mail.gmail.com
Whole thread Raw
In response to Re: Incrementally Updated Backups and restartpoints  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Incrementally Updated Backups and restartpoints  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Wed, Jan 13, 2010 at 9:34 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> No, that's not an issue. We only wait for the backup-end record if we
> haven't seen yet since we started recovery from the base backup.
> Assuming the standby had reached that point already before the new
> backup from the standby started, backupStartLoc is zero in the control file.

OK. That assumption should be documented?

And, when we start an archive recovery from the backup from the standby,
we seem to reach a safe starting point before database has actually become
consistent. It's because backupStartLoc is zero. Isn't this an issue?

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: patch to implement ECPG side tracing / tracking ...
Next
From: "Kevin Grittner"
Date:
Subject: Re: Serializable Isolation without blocking