[Maria-discuss] aria checksum
Hi, I have data which I want to store in the aria storage engine, the data is inserted then never updated or deleted, although the table could be truncated. This data could potentially be replicated in production. The data is inserted in parallel and once the table reaches a certain capacity data is no long inserted into it. My question is, would I want to turn on the checksum for this data? And, if yes, should I use table checksum or page checksum? What are the advantages / disadvantages of this? I tried searching docs and couldn't find a breakdown so if someone could answer this or point me to a doc or discussion that would be great. Right now I am using DYNAMIC row format since I want the smallest footprint possible. thanks, Scott
Scott Feldstein <scottmf76@yahoo.com> writes:
My question is, would I want to turn on the checksum for this data? And, if yes, should I use table checksum or page checksum? What are the advantages / disadvantages of this? I tried searching docs and couldn't find a breakdown so if someone could answer this or point me to a doc or discussion that would be great.
When in doubt, always turn on checksums. Page level means you'll know exactly what page got corrupted while if it was table level, you'll just know "Something in the table is corrupt". The finer grained the better. -- Stewart Smith
participants (2)
-
Scott Feldstein
-
Stewart Smith