On Wed, Jul 15, 2026 at 4:52 AM Andrey Borodin <[email protected]> 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. -- Robert Haas EDB: http://www.enterprisedb.com
v2-0001-Prevent-walsummarizer-from-getting-stuck-at-a-tim.patch
Description: Binary data
