Re: What exactly is our CRC algorithm?

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: What exactly is our CRC algorithm?
Date: 2014-11-07 05:08:04
Message-ID: CAA4eK1J90AzCJPsG9vP-AP0Jjvbrd3-gRGcY33CCPoxdOyK6mw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 4, 2014 at 3:17 PM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
wrote:

> 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.
>>
>>
Will this change allow database created before this commit to be
started after this commit?

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2014-11-07 05:57:13 Re: inherit support for foreign tables
Previous Message Amit Langote 2014-11-07 02:17:05 Re: On partitioning