Re: recovery_target_timeline and multiple slave behavior when master fails - Mailing list pgsql-general

From Fujii Masao
Subject Re: recovery_target_timeline and multiple slave behavior when master fails
Date
Msg-id CAHGQGwE4rqUzAsE6VwcWSMxoX=qTK7gF5K=7y4c3q2zD1kQBLw@mail.gmail.com
Whole thread Raw
In response to recovery_target_timeline and multiple slave behavior when master fails  (Rick Pufky <rick@omniti.com>)
Responses Re: recovery_target_timeline and multiple slave behavior when master fails  (Rick Pufky <rick@omniti.com>)
List pgsql-general
On Fri, Dec 16, 2011 at 3:59 AM, Rick Pufky <rick@omniti.com> wrote:
> Any thoughts on the above snippets? Am I interpreting the documentation
> correctly? Is there any further information needed to debug this?

You need to share the archive directory between all three nodes to use that
trick.

To follow the timeline change that occurs at failover to another standby,
the standby needs to read the timeline history file. This file is created and
archived at failover by new master (i.e., another standby). This file is not
shipped via replication, so the standby needs to read it from the archive.
So you need to have the shared archive directory.

Regards,

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

pgsql-general by date:

Previous
From: "David Johnston"
Date:
Subject: Re: indexes and tables
Next
From: Merlin Moncure
Date:
Subject: Re: Logical Aggregate Functions (eg ANY())