It is getting monotonic but we had another database corruption. It happened on the same database I have been doing these tests on but since this is one of the bigger databases we have that may not be remarkable. Today we used a different recovery approach: instead of restoring a backup (which lags behind up to 24 hours) we did a recover-with-196/restore-with-199 cycle. Luckily that worked.
We can no longer risk any more downtime or worse: losing more client data so we have decided to revert to 196 for now. Nonetheless will I be working on this and if I can do anything to help resolve this issue I will be more than happy to. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/d7ad1a2d-9d0a-4aec-8653-6e03d0bcf5f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
