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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(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 20:46:58
Message-ID: 4B313042.9070103@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> On Wed, 2009-12-23 at 04:15 +0900, Fujii Masao wrote:
>> On Wed, Dec 23, 2009 at 4:09 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>> It's needed to find the place where the backup stopped, so it defines
>>> the safe stopping point. We could easily pass that info via WAL, when
>>> streaming. It doesn't actually matter until we try to failover.
>> Right. And, it's also needed to cooperate with HS which begins accepting
>> read-only queries after a recovery reaches that safe stopping point.
>
> Agreed, hence my interest!

Yeah, that's a great idea.

I was just having a chat with Magnus this morning, and he asked if the
current patch already provides or if it would be possible to write a
stand-alone utility to connect to a master and stream WAL files to an
archive directory, without setting up a full-blown standby instance. We
came to the conclusion that backup history files wouldn't be copied as
the patch stands, because the standby has to specifically request them.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-12-22 20:47:14 Re: Backup history file should be replicated in Streaming Replication?
Previous Message Heikki Linnakangas 2009-12-22 20:37:23 Re: Tuplestore should remember the memory context it's created in