Re: BUG #19432: recovery fails at invalid checkpoint record

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Felix Hamme <felix(dot)hamme(at)ionos(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19432: recovery fails at invalid checkpoint record
Date: 2026-03-16 15:07:51
Message-ID: 1b26be28f1e33162728da58162fcb80874fae4d8.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, 2026-03-16 at 14:56 +0100, Felix Hamme wrote:
> I'm tempted to use a restore_command which does cp for history files
> and mv for WAL files, to optimize performance and disk usage.
> An AI told me that a second restore attempt for the same WAL file
> could only happen if recovery is resumed after a crash.

Don't do that. Make the restore_command idempotent.
Trying to optimize for storage space often causes problems elsewhere.

Yours,
Laurenz Albe

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-03-16 15:51:30 BUG #19435: Error: "No relation entry for relid 2" Triggered by Complex Join with Self-Referencing Tables
Previous Message Felix Hamme 2026-03-16 13:56:03 Re: BUG #19432: recovery fails at invalid checkpoint record