Skip site navigation (1) Skip section navigation (2)

Re: Incrementally Updated Backups and restartpoints

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Incrementally Updated Backups and restartpoints
Date: 2010-01-13 12:34:05
Message-ID: 4B4DBDBD.10304@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-docspgsql-hackers
Fujii Masao wrote:
> On Wed, Jan 13, 2010 at 8:36 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> I wonder if it would be enough to document that pg_control must be
>> backed up first?
> 
> Probably No. The archive recovery from such base backup would always
> fail at the end of recovery because there is no backup-end record,
> i.e., pg_stop_backup() is not executed in that case.

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.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-docs by date

Next:From: Fujii MasaoDate: 2010-01-13 22:13:05
Subject: Re: Incrementally Updated Backups and restartpoints
Previous:From: Fujii MasaoDate: 2010-01-13 11:57:37
Subject: Re: Incrementally Updated Backups and restartpoints

pgsql-hackers by date

Next:From: Hitoshi HaradaDate: 2010-01-13 12:37:43
Subject: Re: More frame options in window functions
Previous:From: Boszormenyi ZoltanDate: 2010-01-13 12:07:42
Subject: Re: lock_timeout GUC patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group