Re: recovery_target_timeline and multiple slave behavior when master fails

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Rick Pufky <rick(at)omniti(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: recovery_target_timeline and multiple slave behavior when master fails
Date: 2011-12-19 02:51:46
Message-ID: CAHGQGwE4rqUzAsE6VwcWSMxoX=qTK7gF5K=7y4c3q2zD1kQBLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Dec 16, 2011 at 3:59 AM, Rick Pufky <rick(at)omniti(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2011-12-19 04:32:09 Re: Logical Aggregate Functions (eg ANY())
Previous Message David Johnston 2011-12-19 00:26:46 Re: indexes and tables