Re: Add a hint to the "WAL summaries are required" errors

From: Manu <manuelreyesbravo(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Raja Sai Pranav <rajasaipranav0(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Subject: Re: Add a hint to the "WAL summaries are required" errors
Date: 2026-11-10 15:19:11
Message-ID: 179432395186.9461.8529919196253424425@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Fujii,

On Mon, Nov 9, 2026 at 7:40 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
wrote:
> HINT: Make sure WAL summarization is enabled. Consider using a more
> recent backup as the basis for this incremental backup,
> or taking a new full backup.

Your wording is better, and the more recent backup option works. In
the five ways I found to hit this error, a full backup taken after the
missing summaries was a good basis: the incremental backup succeeded
and the combined cluster started with all rows, 22 of 22 runs. A
backup from before them failed with the same error in all 22 runs that
had missing summaries, and each time the DETAIL's LSN fell between the
two backups' start LSNs. With your hint applied to master it builds
without warnings, and pg_combinebackup's TAP test 007 passes.

One note on the first sentence: with summarize_wal off, the request
fails earlier with "incremental backups cannot be taken unless WAL
summarization is enabled" (3 of 3), so whoever sees this hint already
has it enabled and the sentence can only be about the past.

Regards,
Manu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2026-11-10 15:19:39 Re: configure picks a clang that doesn't match LLVM_CONFIG
Previous Message Tomás Senart 2026-11-10 15:12:42 [PATCH v1] Match jsonpath variable names exactly when checking mutability