From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
---|---|
To: | Subhankar Chattopadhyay <subho(dot)atg(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgbasebackup necessary for master slave change? |
Date: | 2016-12-08 09:45:42 |
Message-ID: | CAKt_ZftznniipHP8jqk_5_w6UGGVigPP3WY-h1FmMVes-ctOuQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Dec 8, 2016 at 10:33 AM, Subhankar Chattopadhyay <
subho(dot)atg(at)gmail(dot)com> wrote:
> Hi,
>
> Few days back I had asked if it is needed to to pg_basebackup for
> every database update. From John I understood that it is unnecessary
> and if the slave is syncing, even if it is catching up, it would be
> able to sync without doing pg_basebackup. This is working also for me.
>
> However, for a failover scenario, where a master goes down, and I make
> the slave as master, and then when the old master comes back as a
> slave again, if I don't take pg_basebackup from the new master, it
> cannot follow the new master. This is kind of an overhead. Is there a
> way I can make the old master follow the new master without having to
> do full backup?
>
Depending on your version and circumstance, pg_rewind may address your
problem.
https://www.postgresql.org/docs/9.5/static/app-pgrewind.html
>
>
>
> Subhankar Chattopadhyay
> Bangalore, India
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more
From | Date | Subject | |
---|---|---|---|
Next Message | Subhankar Chattopadhyay | 2016-12-08 09:49:39 | Re: pgbasebackup necessary for master slave change? |
Previous Message | Charles Clavadetscher | 2016-12-08 09:34:59 | Re: Who dropped a role? |