Hello. MULTI_THREADED setting is to allow concurrent execution of statements.
MVCC setting is to use row-level locks instead of table-level locks. If it is not in use you should always lock tables in the same order in all transactions. In 1.4.197 MVCC is set by default. However, if you use old PageStore engine for some reason, MVCC should be disabled explicitly, it has issues with this engine (;MV_STORE=FALSE;MVCC=FALSE). Upcoming 1.4.198 does not have this setting any more. MVStore engine uses row-level locks, PageStore uses table-level locks unconditionally. In 1.4.197 MULTI_THREADED is not set by default. You may enable it for MVStore, but be careful, there were issues in some specific use cases. In upcoming 1.4.198 this setting is true by default for MVStore engine (and false for PageStore) and there should be no reason to change its value, MVStore works fine with it and PageStore still has issues with it. You can build H2 from the current sources to achieve better concurrency. https://github.com/h2database/h2database http://h2database.com/html/build.html#building You need a jar target. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
