From: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
---|---|
To: | David Steele <david(at)pgmasters(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, 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>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
Subject: | Re: documenting the backup manifest file format |
Date: | 2020-04-16 22:23:27 |
Message-ID: | 20200417002327.0bb2ef11@firost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 15 Apr 2020 18:54:14 -0400
David Steele <david(at)pgmasters(dot)net> wrote:
> On 4/15/20 6:43 PM, Jehan-Guillaume de Rorthais wrote:
> > On Wed, 15 Apr 2020 12:03:28 -0400
> > Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> >
> >> On Wed, Apr 15, 2020 at 11:23 AM Jehan-Guillaume de Rorthais
> >> <jgdr(at)dalibo(dot)com> wrote:
> >>> But for backup_manifest, it's kind of shame we have to check the checksum
> >>> against an transformed version of the file. Did you consider creating eg.
> >>> a separate backup_manifest.sha256 file?
> >>>
> >>> I'm very sorry in advance if this has been discussed previously.
> >>
> >> It was briefly mentioned in the original (lengthy) discussion, but I
> >> think there was one vote in favor and two votes against or something
> >> like that, so it didn't go anywhere.
> >
> > Argh.
> >
> >> I didn't realize that there were handy command-line tools for manipulating
> >> json like that, or I probably would have considered that idea more
> >> strongly.
> >
> > That was indeed a lengthy thread with various details discussed. I'm sorry I
> > didn't catch the ball back then.
>
> One of the reasons to use JSON was to be able to use command line tools
> like jq to do tasks (I use it myself).
That's perfectly fine. I was only wondering about having the manifest checksum
outside of the manifest itself.
> But I think only the pg_verifybackup tool should be used to verify the
> internal checksum.
true.
> Two thoughts:
>
> 1) You can always generate an external checksum when you generate the
> backup if you want to do your own verification without running
> pg_verifybackup.
Sure, but by the time I want to produce an external checksum, the manifest
would have travel around quite a bit with various danger on its way to corrupt
it. Checksuming it from the original process that produced it sounds safer.
> 2) Perhaps it would be good if the pg_verifybackup command had a
> --verify-manifest-checksum option (or something) to check that the
> manifest file looks valid without checking any files. That's not going
> to happen for PG13, but it's possible for PG14.
Sure.
I just liked the idea to be able to check the manifest using an external
command line implementing the same standardized checksum algo. Without editing
the manifest first. But I understand it's too late to discuss this now.
Regards,
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-04-16 22:31:52 | Re: remove_useless_groupby_columns does not need to record constraint dependencies |
Previous Message | Ranier Vilela | 2020-04-16 22:21:56 | Re: [PATCH'] Variables assigned with values that is never used. |