> On 16 Jul 2026, at 17:19, Robert Haas <[email protected]> wrote: > > In the scenario tested by this test case, recovery works fine. Without > the patch, node3 follows the timeline switch from TLI 1 to TLI 2 and > continues recovery thereafter without a problem. Only WAL > summarization gets stuck. Maybe I need to go read your thread to > figure out why you think these are the same problem, but based on what > the test case does, I feel like they are different problems.
I toyed a bit with your test and it is safe as long as node1 has is own archive. So yes, technically there's no problem. When node3 and node1 has shared archive some write activity triggers problematic behavior. PFA demo test to illustrate this. First step is your v1 patch intact. Step 2 is test change to trigger the problem. Anyway, this happens only when nodes have common archive. Best regards, Andrey Borodin.
vAB1-0001-Prevent-walsummarizer-from-getting-stuck-at-a-t.patch
Description: Binary data
vAB1-0002-DEMO-recovery-follows-the-wrong-timeline-at-a-s.patch
Description: Binary data
