Re: Backup history file should be replicated in Streaming Replication?

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Backup history file should be replicated in Streaming Replication?
Date: 2009-12-22 18:28:21
Message-ID: 3f0b79eb0912221028g42ac2c44k189ef4520add38a4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 23, 2009 at 2:42 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> The backup history file is a slightly bit quirky way of doing things and
> was designed when the transfer mechanism was file-based.
>
> Why don't we just write a new xlog record that contains the information
> we need? Copy the contents of the backup history file into the WAL
> record, just like we do with prepared transactions. That way it will be
> streamed to the standby without any other code being needed for SR,
> while we don't need to retest warm standby to check that still works
> also.

This means that we can replace a backup history file with the corresponding
xlog record. I think that we should simplify the code by making the replacement
completely rather than just adding new xlog record. Thought?

BTW, in current SR code, the capability to replicate a backup history file has
been implemented. But if there is better and simpler idea, I'll adopt it.

Regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-12-22 18:41:20 Re: Backup history file should be replicated in Streaming Replication?
Previous Message Bruce Momjian 2009-12-22 18:20:17 Re: alpha3 release schedule?