Re: Multiple Slave Failover with PITR - Mailing list pgsql-general

From Ken Brush
Subject Re: Multiple Slave Failover with PITR
Date
Msg-id CANCJzPbZ+VhCzdLubhAH4hCoD-E6u7ViP-Tw7YEPDt-fN2yGcQ@mail.gmail.com
Whole thread Raw
In response to Re: Multiple Slave Failover with PITR  (Sergey Konoplev <gray.ru@gmail.com>)
Responses Re: Multiple Slave Failover with PITR  (Sergey Konoplev <gray.ru@gmail.com>)
List pgsql-general
On Wed, Apr 11, 2012 at 9:50 AM, Sergey Konoplev <gray.ru@gmail.com> wrote:
> On Wed, Apr 11, 2012 at 8:12 PM, Ken Brush <kbrush@gmail.com> wrote:
>>>>> 8. Copy the history file from the new master to the slave (it's the
>>>>> most recent #.history file in the xlog directory)
>>>
>>> It will work in the case of archive_command presence only and I will
>>> need to sync the whole pg_xlog content if do not have archive_command
>>> in recovery.conf, correct?
>>
>> The new master will sync out the WAL logs from pg_xlog that the slaves
>> need. The wal sender/receiver system is what I rely on for this.
>
> So you do not have archive_command in recovery.conf, do you?
>

Correct, I do not.

-Ken

pgsql-general by date:

Previous
From: Sergey Konoplev
Date:
Subject: Re: Multiple Slave Failover with PITR
Next
From: Sergey Konoplev
Date:
Subject: Re: Multiple Slave Failover with PITR