| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: walsummarizer can get stuck when switching timelines |
| Date: | 2026-07-15 14:15:59 |
| Message-ID: | CA+TgmoZ3o__hmheSynhrY1kHhQdSUM4+UFD_tZ6EDbGAtVENmw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EDB: http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Prevent-walsummarizer-from-getting-stuck-at-a-tim.patch | application/octet-stream | 16.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-07-15 14:20:19 | Re: Grab bag of smaller OpenSSL fixups |
| Previous Message | Melanie Plageman | 2026-07-15 14:07:18 | Re: Fix FSM range endpoint after relation extension |