Postgres Pro
Downloads
Home   >   mailing lists

Re: New Slave - timeline ERROR - Mailing list pgsql-general

From bricklen
Subject Re: New Slave - timeline ERROR
Date
Msg-id CAGrpgQ8GwGh99DR+zRnFKpnSTWBEvM-=-FhD_V0xkqktBDYcEQ@mail.gmail.com
Whole thread Raw
In response to Re: New Slave - timeline ERROR  ("drum.lucas@gmail.com" <drum.lucas@gmail.com>)
Responses Re: New Slave - timeline ERROR
List pgsql-general
Tree view
On Sat, Jan 9, 2016 at 1:49 PM, drum.lucas@gmail.com <drum.lucas@gmail.com> wrote:
Hi,

If the master is successfully ships WALs to the slave you are setting up you do not need the "stream" option.

yes.. the master is successfully shipping the WALs....

Is there anything else? Help, please hehehehe

If you are able to stop Postgres on the slave you are taking the base backup from, you could do this:

1). Stop postgres on slave1
2). Rsync slave1 to slave2 to copy only the deltas.
3). When you start up slave2 the WALs that the master has shipped to slave2 should apply and bring your system up to consistency.

pgsql-general by date:

Previous
From: "drum.lucas@gmail.com"
Date:
Subject: Re: New Slave - timeline ERROR
Next
From: "drum.lucas@gmail.com"
Date:
Subject: Re: New Slave - timeline ERROR