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

From Thom Brown
Subject Re: walsummarizer can get stuck when switching timelines
Date
Msg-id CAA-aLv6vjnQd84+s7Pgc6LkOwAFDHq++SbQ2a8aa-vKk0sS-DA@mail.gmail.com
Whole thread
In response to Re: walsummarizer can get stuck when switching timelines  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: walsummarizer can get stuck when switching timelines
List pgsql-hackers
On Thu, 16 Jul 2026 at 14:45, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Thu, Jul 16, 2026 at 8:59 AM Thom Brown <thom@linux.com> wrote:
> > Well if we run pg_switch_wal(), we're effectively closing the current
> > segment. CHECKPOINT then emits its WAL after the switch. If the
> > summarizer needs a CHECKPOINT_REDO record in the segment being
> > archived, it would already be too late.
>
> OK, I think this is where we're seeing things differently. The
> summarizer doesn't need a CHECKPOINT_REDO record in the segment being
> archived. Rather, we need a CHECKPOINT_REDO record somewhere after the
> WAL that we want summarized. In this case, the WAL we want summarized
> is generated by the pg_switch_wal() call.

Ah, gotcha. Sorry for the noise.

Thom



pgsql-hackers by date:

Previous
From: ayoub.kazar@data-bene.io
Date:
Subject: Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL
Next
From: ayoub.kazar@data-bene.io
Date:
Subject: Re: [PATCH] Rewrite undirected edge patterns in GRAPH_TABLE using UNION ALL