Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: New CRC algorithm: Slicing by 8
- From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
- To: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>
- Cc: "Gregory Stark" <gsstark(at)mit(dot)edu>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Gregory Maxwell" <gmaxwell(at)gmail(dot)com>, <mark(at)mark(dot)mielke(dot)cc>, "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: Fri, 27 Oct 2006 11:30:52 +0200
- Message-id: <E1539E0ED7043848906A8FF995BDA57901726A5F@m0143.s-mxs.net> <text/plain>
> > > Putting xl_prev to the end helps only for direct IO WAL sync > > > methods, else we would need it on every page. > > > > [There is already an XLogRecPtr on each 8k page.] > > Given that hardware sector size is still 512 bytes, should > there be a way of detecting a missing 512 byte block in the > middle of an 8K block. > The idea of simply writing a serial counter every 512 bytes > seems to be a good way to handle that... No, we have CRC for that. You are not supposed to turn it off when you see a chance, that an 8k block is not whole. Andreas
- References:
- Re: New CRC algorithm: Slicing by 8
- From: Martijn van Oosterhout
- Re: New CRC algorithm: Slicing by 8
- Prev by Date: Re: New CRC algorithm: Slicing by 8
- Next by Date: Re: bug in on_error_rollback !?
- Previous by thread: Re: New CRC algorithm: Slicing by 8
- Next by thread: Re: New CRC algorithm: Slicing by 8
- Indexes: