Re: Re: BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby. - Mailing list pgsql-bugs

From lichuancheng@highgo.com
Subject Re: Re: BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby.
Date
Msg-id 2018122913081786371813@highgo.com
Whole thread Raw
List pgsql-bugs

>It look like the same issue as I reported in BUG #15151.
>https://www.postgresql.org/message-id/flat/152353560977.31233.11406243320876395727%40wrigleys.postgresql.org
>(unfortunately I didn't have time to explore it further then).

>You have good description of what's going on under hood.

Hi,I read the BUG #15151.
You have say that it does not help to restart slave.

But in 15567, either 'restart slave' or 'move the wal segment from master to slave' can make the slave nomal.

pgsql-bugs by date:

Previous
From: Maxim Boguk
Date:
Subject: Re: BUG #15567: Wal receiver process restart failed when a damagedwal record arrived at standby.
Next
From: PG Bug reporting form
Date:
Subject: BUG #15569: decode function is not correclty working in 10.6