On Fri, Mar 20, 2026 at 4:33 AM Xuneng Zhou <[email protected]> wrote: > > After taking a closer look, I'm less certain about this. I'll > investigate further. Could you also explain why you think this is the > case?
The mechanism is in RequestXLogStreaming (walreceiverfuncs.c, around line 276): it explicitly truncates recptr to the segment start before passing it to the walreceiver. So even when both nodes have replayed the same records, the cascade's startpoint lands at the beginning of the next segment while the upstream's GetStandbyFlushRecPtr returns replayPtr somewhere inside the current one. I covered this in more detail in my reply to your previous message. Best regards, Marco
