| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | mark(at)mark(dot)mielke(dot)cc |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: New CRC algorithm: Slicing by 8 |
| Date: | 2006-10-24 14:37:12 |
| Message-ID: | 8650.1161700632@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
mark(at)mark(dot)mielke(dot)cc writes:
> The 5 year claim seems
> decades too short unless they are talking about a newer technology.
I think what Simon is on about is CRCs being routinely used on the cable
between the disk drive and the CPU. When I was involved in this stuff
you usually only got a parity bit on each byte transferred. CRCs for
all disk command/result messages would definitely help close a risk area
--- but that's only one risk of many.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2006-10-24 14:56:00 | Re: Release stamping (Was: [CORE] Schedule for release?) |
| Previous Message | Peter Eisentraut | 2006-10-24 14:34:57 | Re: Release stamping (Was: [CORE] Schedule for release?) |