pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Rushabh Lathia <rushabh.lathia@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Jeevan Chalke <jeevan.chalke@enterprisedb.com>
Cc: vignesh C <vignesh21@gmail.com>
Cc: David Steele <david@pgmasters.net>
Subject: Re: backup manifests
Date: Tue, 19 Nov 2019 08:49:24 -0500
Message-ID: <f2fb57c2-027b-ac0c-583c-738188ebc850@2ndQuadrant.com> (raw)
In-Reply-To: <CAGPqQf3DcmB6OtTpwqayH5bJgMnx2j-r4v2dFR6_=iFiqPq1Sw@mail.gmail.com>
References: <CA+TgmoZV8dw1H2bzZ9xkKwdrk8+XYa+DC9H=F7heO2zna5T6qg@mail.gmail.com>
	<4b6244ea-4094-9055-080b-7afb274bf270@pgmasters.net>
	<CA+TgmobANXUCZ1XrLJQbX95e3fJa0dRqV09Scjb2kmqt+gdkvg@mail.gmail.com>
	<b2b696b4-b11f-e954-c86a-8252a62a2e40@pgmasters.net>
	<CA+TgmobZrNYR-ATtfZiZ_k-W7tSPgvmYZmyiqumQig4R4fkzHw@mail.gmail.com>
	<146910fc-3df7-eeb4-ac5b-2f57a01f646f@pgmasters.net>
	<CA+TgmoYZDTHbSpwZtW=JDgAhwVAYvmdSrRUjOd+AYdfNNXVBDg@mail.gmail.com>
	<CALDaNm0pReK3ENbadRM=CJXNLsw4tm-MfaK_ckE7RMYEp9pgQg@mail.gmail.com>
	<CAM2+6=VHWifa=+8mtnFy3dqFvQtsEQPy9NBQEv-FbR26L22+uQ@mail.gmail.com>
	<CA+Tgmob1c3Lg4yQmMUwWh5vw67ZvB2HUJXfHGP+Opi+LDzq_bQ@mail.gmail.com>
	<CAGPqQf3DcmB6OtTpwqayH5bJgMnx2j-r4v2dFR6_=iFiqPq1Sw@mail.gmail.com>


On 11/19/19 5:00 AM, Rushabh Lathia wrote:
>
>
> My colleague Suraj did testing and noticed the performance impact
> with the checksums.   On further testing, he found that specifically with
> sha its more of performance impact.  
>
>

I admit I haven't been following along closely, but why do we need a
cryptographic checksum here instead of, say, a CRC? Do we think that
somehow the checksum might be forged? Use of cryptographic hashes as
general purpose checksums has become far too common IMNSHO.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services






view thread (243+ messages)  latest in thread

Message-ID: <f2fb57c2-027b-ac0c-583c-738188ebc850@2ndQuadrant.com>
Permalink:  ../f2fb57c2-027b-ac0c-583c-738188ebc850@2ndQuadrant.com/
Also on:    postgresql.org/message-id/f2fb57c2-027b-ac0c-583c-738188ebc850@2ndQuadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: andrew.dunstan@2ndquadrant.com, rushabh.lathia@gmail.com, robertmhaas@gmail.com, jeevan.chalke@enterprisedb.com, vignesh21@gmail.com, david@pgmasters.net
  Subject: Re: backup manifests
  In-Reply-To: <f2fb57c2-027b-ac0c-583c-738188ebc850@2ndQuadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox