We have MVCC as false and still see the same problem appearing today. The database is corrupt now and we are required to go afresh :(
Any suggestions would be really helpful. Thanks in advance On Friday, September 6, 2013 3:24:34 PM UTC+5:30, Sanjeev Gour wrote: > > Ok, we shall try removing that to avoid even a rare case of databacse > corruption. > On Sep 6, 2013 3:19 PM, "Noel Grandin" <[email protected] <javascript:>> > wrote: > >> >> On 2013-09-06 11:43, Sanjeev Gour wrote: >> >>> >>> (2) turn off MVCC - Would it cause the read/write to the database to >>> become noticeably slow? >>> >>> >> It shouldn't. >> We're pretty fast even in our default mode. >> >> MVCC is mostly useful for applications with very high concurrency >> requirements and where the read/write ratio is very high. >> >> Thomas is working on a replacement engine, and when that is ready, we >> will deprecate the existing engine and remove the MVCC option. >> > -- 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.
