Re: What exactly is our CRC algorithm?

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: What exactly is our CRC algorithm?
Date: 2014-11-04 09:47:18
Message-ID: 5458A0A6.9060407@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2014-11-04 10:07:19 Re: BRIN indexes - TRAP: BadArgument
Previous Message Andres Freund 2014-11-04 08:56:31 Re: tracking commit timestamps