Doing some experiments with LOG=0, killing the process during a transaction loses all of the data since the last close. Like
open transaction A close open transaction B transaction C <- killed with -9 will leave the db with transaction A. Transaction B can be recovered with the recover tool, but there's no indication on start that the previous shutdown wasn't clean, unless I check for the lock file, or something. On Friday, May 30, 2014 5:43:39 AM UTC-7, Brian Craft wrote: > > UNDO_LOG controls rollback, and LOG controls durability? Is that right? > > If I'm doing inserts that should be atomic, but the data is already > persisted elsewhere, can I safely set LOG=0? If we lose power I don't care > that h2 drops data on the floor, so long as it's atomic. I can detect that > the data needs to be reloaded. If it is only half loaded, though, I have > problems. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
