Re: Multiple Slave Failover with PITR

From: Ken Brush <kbrush(at)gmail(dot)com>
To: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Multiple Slave Failover with PITR
Date: 2012-04-11 17:08:38
Message-ID: CANCJzPbZ+VhCzdLubhAH4hCoD-E6u7ViP-Tw7YEPDt-fN2yGcQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Wed, Apr 11, 2012 at 9:50 AM, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> wrote:
> On Wed, Apr 11, 2012 at 8:12 PM, Ken Brush <kbrush(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sergey Konoplev 2012-04-11 17:10:32 Re: Multiple Slave Failover with PITR
Previous Message Sergey Konoplev 2012-04-11 16:50:10 Re: Multiple Slave Failover with PITR

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergey Konoplev 2012-04-11 17:10:32 Re: Multiple Slave Failover with PITR
Previous Message Sergey Konoplev 2012-04-11 16:50:10 Re: Multiple Slave Failover with PITR