Re: How to make sure I don't write a corrupt page to db when I checkpoint?

Sune wrote:

>> Then you run the risk of corruption.

checksums?

As in, a process that modifies a page has to generate a checksum for the modified page, and the process that writes the pages (is there one - it's an in-memory database) has to lock the page and verify the checksum (and, maybe, worry about whether a process modified the page while it was locked by ignoring the lock).

In the context of a DBMS, paranoia is good. Just because you can't see that the processes attached to the database aren't out to make life difficult for you doesn't mean they aren't going to make difficult for you anyway.

-- 
Jonathan Leffler                   #include <disclaimer.h>
Email: jleffler_at_earthlink.net, jleffler_at_us.ibm.com
Guardian of DBD::Informix v2007.0226 -- http://dbi.perl.org/