Alvaro Herrera <[email protected]> writes: > Oh, but also I think I should push a mitigation in case a production > system hits this problem: maybe reduce the message from FATAL to WARNING > if the registered LSN is at a page boundary.
Uh, why? The fix should remove the problem, and if it doesn't, we're
still looking at inconsistent WAL aren't we?
regards, tom lane
