Re: New Slave - timeline ERROR

From: "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: New Slave - timeline ERROR
Date: 2016-01-09 22:10:37
Message-ID: CAE_gQfW-SHfKDECTWznRh7Esu0C96ZoWzDS+MKr3JMiwJ=_q_g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hmm... I see...
>
>
>> Depending on when you took the base backup and how many changes have
>> occurred at your source (slave1) database cluster, the rsync execution time
>> may or may not take as long as a new base backup if is only only shipping
>> deltas (changed files).
>
>
I could stop the slave then.... But I'm afraid getting it back online and
get some other errors hehehehe =\

Lucas Possamai

kinghost.co.nz
<http://forum.kinghost.co.nz/memberlist.php?mode=viewprofile&u=2&sid=e999f8370385657a65d41d5ff60b0b38>

On 10 January 2016 at 10:59, bricklen <bricklen(at)gmail(dot)com> wrote:

> On Sat, Jan 9, 2016 at 1:54 PM, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)com
> > wrote:
>
>> Hi,
>>
>> If you are able to stop Postgres on the slave you are taking the base
>>> backup from, you could do this:
>>
>>
>> I'm not... the data base is 2 TB.
>> So, a RSYNC would take DAYS..... And I'm not able to stop the SLAVE for
>> that long time
>>
>
> Depending on when you took the base backup and how many changes have
> occurred at your source (slave1) database cluster, the rsync execution time
> may or may not take as long as a new base backup if is only only shipping
> deltas (changed files).
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message bricklen 2016-01-09 22:19:41 Re: New Slave - timeline ERROR
Previous Message bricklen 2016-01-09 21:59:41 Re: New Slave - timeline ERROR