Re: backup manifests

From: David Steele <david(at)pgmasters(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Tels <nospam-pg-abuse(at)bloodgate(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>
Subject: Re: backup manifests
Date: 2020-03-30 00:48:58
Message-ID: 030216ce-3781-4bfb-d484-33d1a0c3aae3@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/29/20 8:33 PM, Robert Haas wrote:
> On Fri, Mar 27, 2020 at 4:32 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>> FWIW, I was thinking of backup_manifest.checksum potentially being
>> desirable for another reason: The need to embed the checksum inside the
>> document imo adds a fair bit of rigidity to the file format. See
>
> Well, David Steele suggested this approach. I didn't particularly like
> it, but nobody showed up to agree with me or propose anything
> different, so here we are. I don't think it's the end of the world.

I prefer the embedded checksum even though it is a pain. It's a lot less
likely to go missing.

--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-03-30 00:53:46 Re: fix for BUG #3720: wrong results at using ltree
Previous Message Robert Haas 2020-03-30 00:47:40 Re: backup manifests