> On 2 Aug 2026, at 21:00, Alexander Lakhin <[email protected]> wrote: > > So it looks like the test might fail when the checkpoint record slips into > segment 4. I think swapping two SQL statements would be enough: $node2->safe_psql('postgres', <<EOM); -SELECT pg_switch_wal(); CHECKPOINT; +SELECT pg_switch_wal(); EOM The CHECKPOINT is what gives the summarizer a redo point to close the timeline-2 summary at, and node3 only ever reads completed segments from the archive, so it has to be before pg_switch_wal(). CI shows no problems with this change to me. Best regards, Andrey Borodin.
- Re: walsummarizer can get stuck... Robert Haas
- Re: walsummarizer can get stuck when switching timeli... Robert Haas
- Re: walsummarizer can get stuck when switching timeli... Andrey Borodin
- Re: walsummarizer can get stuck when switching t... Andrey Borodin
- Re: walsummarizer can get stuck when switchi... Robert Haas
- Re: walsummarizer can get stuck when swi... Amit Kapila
- RE: walsummarizer can get stuck when swi... Zhijie Hou (Fujitsu)
- Re: walsummarizer can get stuck when... Robert Haas
- Re: walsummarizer can get stuck... Robert Haas
- Re: walsummarizer can get stuck... Alexander Lakhin
- Re: walsummarizer can get stuck... Andrey Borodin
