Re: Re: BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby.

From: "lichuancheng(at)highgo(dot)com" <lichuancheng(at)highgo(dot)com>
To: Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Re: BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby.
Date: 2018-12-29 05:08:18
Message-ID: 2018122913081786371813@highgo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-12-31 03:29:30 BUG #15569: decode function is not correclty working in 10.6
Previous Message Maxim Boguk 2018-12-29 03:59:34 Re: BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby.