public inbox for [email protected]  

help / color / mirror / Atom feed

From: Fujii Masao <[email protected]>
To: Heikki Linnakangas <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: [email protected]
Subject: Re: [HACKERS] Incrementally Updated Backups and restartpoints
Date: Fri, 26 Mar 2010 22:21:42 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Thu, Mar 4, 2010 at 9:00 PM, Fujii Masao <[email protected]> wrote:
>> 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?
>
> This issue seems to still happen. So should this be fixed for 9.0?
> Or only writing a note in document is enough for 9.0? I'm leaning
> towards the latter.

I'm thinking of adding something like the following to the section
"25.6. Incrementally Updated Backups". Thought?


    The pg_control file must be backed up first.
    This avoids the problem that we might fail to restore a consistent
    database state because recovery starts from the later restart point
    than the start of the backup.

    When recovering from the incrementally updated backup, the server
    can begin accepting connections and complete the recovery successfully
    before the database has become consistent. To avoid these problems,
    you must check whether the database has been consistent by comparing
    the progress of the recovery with the backup ending WAL location
    before your users try to connect to the server and when archive
    recovery ends. So, in advance, the backup ending WAL location must
    be taken by calling the pg_last_xlog_replay_location function at the
    end of the backup. The progress of the recovery is also taken from
    the pg_last_xlog_replay_location function.

Regards,

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

view thread (6+ messages)

reply

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] Incrementally Updated Backups and restartpoints
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox