Re: Logical replication failed recovery - Mailing list pgsql-general

From Pavan Teja
Subject Re: Logical replication failed recovery
Date
Msg-id CACh9nsYmQwcgsioBK3t_m-r8LOFjstqw6LaPwTZiZo5+_LDRGw@mail.gmail.com
Whole thread Raw
In response to Logical replication failed recovery  (Lou Tseng <ltseng@advancedpricing.com>)
List pgsql-general
Hi Lou,

Try setting wal_keep_segments parameter to a higher value. I think it will suffice to solve the problem.

Regards, 
Pavan Teja, 
9841380956 

On Sun, 7 Apr, 2019, 6:53 PM Lou Tseng, <ltseng@advancedpricing.com> wrote:
Hi folks,

Is there a good tutorial to recover from logical replication out of sync?  We ran into this error stating WAL has been removed and now replica is out of sync.  Also, is there a way to increase the number of WAL kept on the master?

Thanks!

2019-04-07 12:28:37.180 UTC [22292] ERROR:  could not receive data from WAL stream: ERROR:  requested WAL segment 0000000100005208000000EB has already been removed

2019-04-07 12:28:37.182 UTC [114186] LOG:  worker process: logical replication worker for subscription 8907992 (PID 22292) exited with exit code 1


Lou Tseng

ltseng@advancedpricing.com
Advanced Medical Pricing Solutions
35 Technology Parkway South, Suite. 100
Peachtree Corners, GA 30092

pgsql-general by date:

Previous
From: Lou Tseng
Date:
Subject: Logical replication failed recovery
Next
From: Sherrylyn Branchaw
Date:
Subject: Re: pg_upgrade --jobs