Re: walsummarizer can get stuck when switching timelines

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: walsummarizer can get stuck when switching timelines
Date: 2026-07-16 05:49:24
Message-ID: CAA4eK1+1TFdQbiuOsP+_=nTWwGZokHTtsw3mj4zf31bAv8onzg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 15, 2026 at 7:46 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Wed, Jul 15, 2026 at 4:52 AM Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> > I can reproduce it locally by adding an extra WAL switch on node1
> > before promoting node2. It can probably be made deterministic either by
> > polling pg_stat_archiver before relying on the segment (as
> > 025_stuck_on_old_timeline.pl does) or by setting archive_mode=always on
> > node2 (I would expect it to be a bit faster).
>
> archive_mode=always seems like the correct fix. Here's v2.
>

Thanks for the updated patch, it works for me.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-07-16 05:56:48 Re: pgstat: add pgstat_prep_pending() for entry ref pending setup
Previous Message Nisha Moond 2026-07-16 05:44:01 Re: Support EXCEPT for TABLES IN SCHEMA publications