| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Incrementally Updated Backups and restartpoints |
| Date: | 2010-01-13 22:13:05 |
| Message-ID: | 3f0b79eb1001131413v4ccc8ac1jf25a1f75cf71d5ce@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Wed, Jan 13, 2010 at 9:34 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Shinnick | 2010-01-16 20:17:22 | Misspelling in index - 8.4.2 manual downloads and on web |
| Previous Message | Heikki Linnakangas | 2010-01-13 12:34:05 | Re: Incrementally Updated Backups and restartpoints |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-01-13 22:20:40 | Re: Serializable Isolation without blocking |
| Previous Message | Robert Haas | 2010-01-13 22:05:06 | Re: patch to implement ECPG side tracing / tracking ... |