Restart replicated slave procedure

From: Joseph Kregloh <jkregloh(at)sproutloud(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Restart replicated slave procedure
Date: 2014-08-22 15:38:36
Message-ID: CAAW2xfe5Mjr6nFrSJHkaxEd_WdG2bGSB61mFLwBypg4NpEQ5Hg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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
issue a new pg_base_backup() or set the master to pg_start_backup() do an
rsync and stop using pg_stop_backup(). If there is a way to avoid any of
that, for example pause replication to hold all the wal files until the
replicated slave comes back and then release them once the replicated slave
is up.

I apologize if this question has already been asked. I did some searching
beforehand.

Thanks,
-Joseph Kregloh

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hubert depesz lubaczewski 2014-08-22 16:29:00 deadlock in single-row select-for-update + update scenario? How could it happen?
Previous Message Tom Lane 2014-08-22 15:20:05 Re: postgres_fdw: Running default expressions on foreign server