From: | bricklen <bricklen(at)gmail(dot)com> |
---|---|
To: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Re-sync slave server |
Date: | 2016-06-07 16:05:20 |
Message-ID: | CAGrpgQ8ag62=1TMEDBTe5SoNjU8xid3OOzDq=A1LRfc5JoQLGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jun 6, 2016 at 5:32 PM, Patrick B <patrickbakerbr(at)gmail(dot)com> wrote:
> My set up:
>
>
> Master --> slave01 (streaming replication) --> slave02 (streaming
> replication)
> Master --> slave03 (wal_files 4 days old, not streaming replication)
>
> The wal_files are stored into each server.
> But when the slave03 was down, the wal_files weren't being copied into it.
> We took too long to discover that, and now we lost some wal_files.. they've
> been recycled...
>
> So my question is:
>
> Can I just do a RE-SYNC from slave01 to slave03 of the data folder?
> Or do I have to sync all the database again?
>
>
If the master is successfully shipping WALs to slave03 now, re-syncing that
replica from slave01 (or slave02) should work fine. By "re-sync" I assume
you mean a full filesystem copy using pg_basebackup etc.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-06-07 18:01:01 | Re: Postgres Dropped DB have recovered files how to restore |
Previous Message | Adrian Klaver | 2016-06-07 13:44:38 | Re: Re-sync slave server |