Re: walsummarizer can get stuck when switching timelines - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: walsummarizer can get stuck when switching timelines
Date
Msg-id A44B14F1-DE37-4E45-BEB4-FAC362A1E2EC@yandex-team.ru
Whole thread
In response to Re: walsummarizer can get stuck when switching timelines  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers

> On 16 Jul 2026, at 17:19, Robert Haas <robertmhaas@gmail.com> 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.


Attachment

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Raise default track_activity_query_size to 16kB (from 1kB, unchanged since 8.x)
Next
From: Etsuro Fujita
Date:
Subject: Re: use of SPI by postgresImportForeignStatistics