| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(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 07:42:07 |
| Message-ID: | 545C77CF.5090608@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/07/2014 07:08 AM, Amit Kapila wrote:
> 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?
No. You could use pg_resetxlog to fix the WAL, but I think at least
relmap files would still prevent you from starting up. You could use
pg_upgrade.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | furuyao | 2014-11-07 07:54:50 | Re: inherit support for foreign tables |
| Previous Message | Andres Freund | 2014-11-07 07:29:19 | Re: Proposal: Log inability to lock pages during vacuum |