> On 2 Jul 2026, at 20:59, surya poondla <[email protected]> wrote: > > I finally got some time to review this patch.
Hi Surya, Thank you for the review! PFA v3. The code now stops after trying the newest timeline eligible for the requested segment. The comment explains why a parent copy of the switch-point segment cannot be used as a whole even though its prefix is valid. A DEBUG1 message makes the resulting wait explicit. Both tests now first prove that recovery reaches the missing child segment and refuses the available parent copy. They then publish the correct child segment, let recovery reach the requested timeline, and check the exact rows, including the absence of divergent parent rows. I left the separate walreceiver state change out of v3. Maybe, I will discuss it in a separate thread. Restart of the walreceiver itself is not such a big problem as not reaching target timeline. Thank you! Best regards, Andrey Borodin.
v3-0001-Prevent-archive-recovery-from-reading-divergent-W.patch
Description: Binary data
