PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID15412
PG Version10.4
OSUbuntu 16.04.4 LTS
Opened2018-10-01 08:38:23+00
Reported byTimur Luchkin
StatusOpen

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      15412
Logged by:          Timur Luchkin
Email address:      (redacted)
PostgreSQL version: 10.4
Operating system:   Ubuntu 16.04.4 LTS
Description:        

Hello. 
Sorry to post it again, but I really need help to recover broken replica. 
LOG:  invalid contrecord length 861 at 159E/A6FFFC40

We are getting this kind of error in WAL based replica's log after the
master DB was down due to no space left issue. 
Disk space was already added and master up'n'running (including its
synchronous streaming based replica), but offsite WAL replica can't start
due to above mentioned error. 
We can't recreate it using pg_basebackup due to slow network and huge DB
size. 
Are there any fixes possible to continue apply WALs?

More details:
<2018-09-25 08:07:19 UTC--- [app:,pid:19517,00000]>LOG:  restored log file
"000000010000159E000000A6" from archive
<2018-09-25 08:07:23 UTC--- [app:,pid:19517,00000]>LOG:  restored log file
"000000010000159E000000A7" from archive
<2018-09-25 08:07:23 UTC--- [app:,pid:19517,00000]>LOG:  invalid contrecord
length 861 at 159E/A6FFFC40

Messages

DateAuthorSubject
2018-10-01 08:38:23+00=?utf-8?q?PG_Bug_reporting_form?=BUG #15412: "invalid contrecord length" during WAL replica recovery
2018-10-01 09:06:46+00Michael PaquierRe: BUG #15412: "invalid contrecord length" during WAL replica recovery
2018-10-12 07:20:29+00Kyotaro HORIGUCHIRe: BUG #15412: "invalid contrecord length" during WAL replica recovery