On Sat, Aug 23, 2014 at 2:18 AM, Joseph Kregloh
wrote:
>
>
> On Fri, Aug 22, 2014 at 2:21 PM, Jerry Sievers
> wrote:
>
>> Joseph Kregloh writes:
>>
>> > Hi,
>> >
>> > Currently I am doing asynchronous replication from master to
>> > slave. Now if I restart the slave it will fall out of sync wit
On Fri, Aug 22, 2014 at 3:47 PM, Jerry Sievers
wrote:
> Yes, changing archive_command to '' or something that returns false will
> let you queue the WALs until reverting the change.
>
> I am assuming you run a version where the archive_mode setting exists
> which will be set to 'on' and left that
On Fri, Aug 22, 2014 at 2:21 PM, Jerry Sievers
wrote:
> Joseph Kregloh writes:
>
> > Hi,
> >
> > Currently I am doing asynchronous replication from master to
> > slave. Now if I restart the slave it will fall out of sync with the
> > master. Is there a correct procedure or set of steps to avoid
Joseph Kregloh writes:
> Hi,
>
> Currently I am doing asynchronous replication from master to
> slave. Now if I restart the slave it will fall out of sync with the
> master. Is there a correct procedure or set of steps to avoid this? I
> am looking for best practices or suggestions. Whenever my s
Hi,
Currently I am doing asynchronous replication from master to slave. Now if
I restart the slave it will fall out of sync with the master. Is there a
correct procedure or set of steps to avoid this? I am looking for best
practices or suggestions. Whenever my slave fell out of sync I would either
