Re: Add recovery to pg_control and remove backup_label - Mailing list pgsql-hackers

From David Steele
Subject Re: Add recovery to pg_control and remove backup_label
Date
Msg-id 75071637-6b5c-483b-ac55-9c15b69eaca0@pgmasters.net
Whole thread Raw
In response to Re: Add recovery to pg_control and remove backup_label  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Add recovery to pg_control and remove backup_label
List pgsql-hackers
On 11/20/23 15:47, Robert Haas wrote:
> On Mon, Nov 20, 2023 at 2:41 PM David Steele <david@pgmasters.net> wrote:
>> I can't see why a backup would continue to be valid without a manifest
>> -- that's not very standard for backup software. If you have the
>> critical info in backup_label, you can't afford to lose that, so why
>> should backup_manifest be any different?
> 
> I mean, you can run pg_basebackup --no-manifest.

Maybe this would be a good thing to disable for page incremental. With 
all the work being done by pg_combinebackup, it seems like it would be a 
good idea to be able to verify the final result?

I understand this is an option -- but does it need to be? What is the 
benefit of excluding the manifest?

Regards,
-David



pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: Parallel CREATE INDEX for BRIN indexes
Next
From: Andres Freund
Date:
Subject: Re: Annoying build warnings from latest Apple toolchain