On Sun, 2026-09-13 at 16:30 +0300, Konstantin Knizhnik wrote:
> A physical standby can get stuck forever if local pg_wal contains a
> corrupt record that walreceiver has already reported as flushed.
> What happens:
I can't help but ask: how did it get corrupted? Is it also corrupted on
the primary? What kinds of failures can cause this situation?
There seems to already be some kind of policy that we should try to re-
fetch bad records. Are you extending that policy or filling in an
implementation gap?
Regards,
Jeff Davis
