| From: | soumitra bhandary <soumitra(dot)bhandary(at)hotmail(dot)com> |
|---|---|
| To: | Mai Peng <maily(dot)peng(at)webedia-group(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Important lag in replication streaming between master and standby |
| Date: | 2019-08-26 15:45:52 |
| Message-ID: | BMXPR01MB36396E8CF476E66D72D84F9CE0A10@BMXPR01MB3639.INDPRD01.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi Mai,
It seems that the wal log requested by slave is not available in master’s wal directory.
In that case if the DB is archival mode the same wal can be found there and configure slave accordingly so that it can read wal from archive location.
Sent from my iPhone
> On 26-Aug-2019, at 8:51 PM, Mai Peng <maily(dot)peng(at)webedia-group(dot)com> wrote:
>
> Hello,
>
> I’ve got several times this error : "requested WAL segment 000000020000A01A0000004F has already been remove". I think it’s due to the lag between our master in EU zone and our standby in US zone.
> How could we configure Postgres to handle this issue?
> Thx a lot
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2019-08-27 07:42:44 | Re: Important lag in replication streaming between master and standby |
| Previous Message | Jeff Janes | 2019-08-26 15:43:16 | Re: Important lag in replication streaming between master and standby |