Re: What exactly is our CRC algorithm? - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: What exactly is our CRC algorithm?
Date
Msg-id 5458A0A6.9060407@vmware.com
Whole thread Raw
In response to Re: What exactly is our CRC algorithm?  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: What exactly is our CRC algorithm?  (Robert Haas <robertmhaas@gmail.com>)
Re: What exactly is our CRC algorithm?  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 10/27/2014 06:02 PM, Heikki Linnakangas wrote:
> I came up with the attached patches. They do three things:
>
> 1. Get rid of the 64-bit CRC code. It's not used for anything, and
> haven't been for years, so it doesn't seem worth spending any effort to
> fix them.
>
> 2. Switch to CRC-32C (Castagnoli) for WAL and other places that don't
> need to remain compatible across major versions.
>
> 3. Use the same lookup table for hstore and ltree, as used for the
> legacy "almost CRC-32" algorithm. The tables are identical, so might as
> well.
>
> Any objections?

I hear none, so committed with some small fixes.
- Heikki




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: tracking commit timestamps
Next
From: Jeff Janes
Date:
Subject: Re: BRIN indexes - TRAP: BadArgument