| From: | bricklen <bricklen(at)gmail(dot)com> |
|---|---|
| To: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(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 21:53:10 |
| Message-ID: | CAGrpgQ8GwGh99DR+zRnFKpnSTWBEvM-=-FhD_V0xkqktBDYcEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jan 9, 2016 at 1:49 PM, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | drum.lucas@gmail.com | 2016-01-09 21:54:56 | Re: New Slave - timeline ERROR |
| Previous Message | drum.lucas@gmail.com | 2016-01-09 21:49:16 | Re: New Slave - timeline ERROR |