From: | Fabrízio de Royes Mello <fabrizio(at)timbira(dot)com(dot)br> |
---|---|
To: | PegoraroF10 <marcos(at)f10(dot)com(dot)br> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Replication pull instead of push |
Date: | 2018-03-07 19:38:20 |
Message-ID: | CAPfkCSCC_ubW8JQAoqNmWdxWG2+F-+jbYd4__kch6iVouFhfuQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2018-03-07 16:01 GMT-03:00 PegoraroF10 <marcos(at)f10(dot)com(dot)br>:
>
> We have several servers, our masters, installed on several cities. Then we
> need have a centralized database (our standby) where we can do our
reports.
> So, usual way of doing postgres replication is creating a
> replication/subscription process.
Ok.
> But then that master server should be reachable and sometimes it´s not,
just
> because their IP changed or because we need to configure its router to get
> Postgres server properly.
>
> Finally my question, there is a way to pull data which needs to be
> replicated from master to slave.
>
The way is fix your network connection and if necessary change your
subscription side do connect again in your server and continue pulling data.
If you don't drop your publication it will retain the WAL until the
subscription connect again and pull data.
Regards,
--
Fabrízio de Royes Mello Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From | Date | Subject | |
---|---|---|---|
Next Message | PegoraroF10 | 2018-03-07 19:49:38 | Re: Replication pull instead of push |
Previous Message | PegoraroF10 | 2018-03-07 19:01:33 | Replication pull instead of push |