Re: Avoid truncated or zero-padded copies of replaced files in backups.

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: David Steele <david(at)pgbackrest(dot)org>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Avoid truncated or zero-padded copies of replaced files in backups.
Date: 2026-10-25 23:32:29
Message-ID: CAGRkXqQkXmNXv0tKr2QK42GhiPBknFLgENcg=1Nf7FmFRwhePQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi David,

Agreed. This is an old bug on its own and not a backup issue, so it
should not hold up your patch. I will start a separate thread for it
with your comments addressed.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2026-10-25 23:37:31 A bug in recovery prefetcher, triggering asserts / FATAL: checkpoint request failed
Previous Message shihao zhong 2026-10-25 22:56:42 Re: UNDO with FILEOPS, and the FLUX table AM