Hi,
>From time to time, people send reports about corrupt databases. Of
course it's not acceptable that databases get corrupt, and my top
priority always was to ensure this can not occur. I wrote many test
cases. With the new storage format ('page store') many problems have
been solved, but not all. But until recently I could not reproduce
such problems, even using a Christmas light timer (switching off power
while the database is running).
But now I found a much better way to test it, by using a special file
system that simulates stopping a process after each write (trying to
recover after each write operation). I did already have 'power
failure' tests since a long time, but with the special file system I
can (more or less efficiently) run this against almost all
applications (re-using all existing test cases).
Unfortunately, I did find a way to corrupt a database by killing a
process. The probability is relatively low (less than 1 in 1000
cases). The most problematic part seems to be closing the database. My
top priority is currently to fix those issues, and run more tests.
Regards,
Thomas
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
