From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | Aviel Buskila <aviel33(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: fixing failed master after standby promotion |
Date: | 2016-08-08 02:35:41 |
Message-ID: | CAD21AoBpOrmozDp=vE+jdFsfk0XtCRgNUbSTn9G6eR=A+hdBow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Aug 7, 2016 at 10:55 PM, Aviel Buskila <aviel33(at)gmail(dot)com> wrote:
> Hey ,
> I have been setting a configuration of 2 nodes (master and standby)
> replicating using repmgr, and 1 server using for load balancing using
> pgpool-II.
> Now after the master has failed, the standby was successfully promoted.
> I would like to know if there is any elegant way to semi-automatically
> resync the failed master and re-register him as a standby server?
>
I'm not familiar with repmgr but you can use the pg_rewind in order to
automatically synchronize a data cluster if you use PostgreSQL 9.5 or
later.
In 9.4 or before, you need to take whole backup from the new master
server, for example using pg_basebackup.
Regards,
--
Masahiko Sawada
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-08-08 02:56:11 | Re: fixing failed master after standby promotion |
Previous Message | Patrick B | 2016-08-08 01:22:51 | Re: pg_archivecleanup standalone bash script |