From: | Subhankar Chattopadhyay <subho(dot)atg(at)gmail(dot)com> |
---|---|
To: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgbasebackup necessary for master slave change? |
Date: | 2016-12-08 10:01:00 |
Message-ID: | CAPg1NnGsPD=6XyJEffxGF-yubuKRTGn-Jk=JwYynEniaw_OUkQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
pg_rewind cannot be used as I am on 9.4.
Anything else?
On Thu, Dec 8, 2016 at 3:23 PM, Achilleas Mantzios
<achill(at)matrix(dot)gatewaynet(dot)com> wrote:
> On 08/12/2016 11:33, Subhankar Chattopadhyay 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?
>
> pg_rewind
>>
>>
>>
>>
>> Subhankar Chattopadhyay
>> Bangalore, India
>>
>>
>
>
> --
> Achilleas Mantzios
> IT DEV Lead
> IT DEPT
> Dynacom Tankers Mgmt
>
>
>
>
> --
> 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
--
Subhankar Chattopadhyay
Bangalore, India
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2016-12-08 10:08:47 | Re: pgbasebackup necessary for master slave change? |
Previous Message | Achilleas Mantzios | 2016-12-08 09:53:47 | Re: pgbasebackup necessary for master slave change? |