Re: Add system identifier to backup manifest - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Add system identifier to backup manifest
Date
Msg-id ZaiK4WD5gPD4MMUX@paquier.xyz
Whole thread Raw
In response to Re: Add system identifier to backup manifest  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Jan 17, 2024 at 08:46:09AM -0500, Robert Haas wrote:
> On Wed, Jan 17, 2024 at 6:45 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>> Hmm, okay, but what if I take a full backup from a primary server and
>> later I want an incremental from a standby, or the other way around?
>> Will this prevent me from using such a combination?
>
> The system identifier had BETTER match in such cases. If it doesn't,
> somebody's run pg_resetwal on your standby since it was created... and
> in that case, no incremental backup for you!

There is an even stronger check than that at replay as we also store
the system identifier in XLogLongPageHeaderData and cross-check it
with the contents of the control file.  Having a field in the backup
manifest makes for a much faster detection, even if that's not the
same as replaying things, it can avoid a lot of problems when
combining backup pieces.  I'm +1 for Amul's patch concept.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: torikoshia
Date:
Subject: Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)
Next
From: Richard Guo
Date:
Subject: Re: Strange Bitmapset manipulation in DiscreteKnapsack()