On Nov 23, 11:43 pm, Thomas Mueller <[email protected]> wrote: > OK, then I suggest to use online backups, or another database that is > well tested for power down
Well, I appreciate your honesty. For the moment I'm still liking H2 database. But hey, yes, that 1% may kill me ;-) I'll try going for the scenario in which problems are just the least likely. We've already resorted to using the "...ORDER BY ID, ID" workaround. Somewhere down this discussion you've mentioned the automatic re- generation of indexes on startup. It appears that I'm accidently having those (first fixed in 1.1.112). Would that something to want after a restart, given that those may still often be triggered by a power-down, hence possibly corrupting my indexes? Is there some kind of switch starting 1.1.112? Another thing to do then would be to go to 1.2.x, given that you've started testing kill -9 scenarios. Are there any other measures that you can recommend to: 1. Reduce the chance on reoccurence? 2. Be able to post the best possible reports whenever this happens again in the future? Thanks again, Sander. -- 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=.
