Hi, As I understand the difference between this options MVCC: all sql commands executes with database level locking (one command per database at once) but in transaction if you've modified some table it will be unlocked for an other sessions without waiting for commit with correct data visibility for all the parties. MULTI_THREADED: uses session level lock (multiple sessions can execute commands in parallel but it will not increase throughput if you want to concurrently update one table because of table level locking though selects will not block each other) but when you've modified some table it will be locked until commit or rollback will be executed. So the best thing would be MVCC+MULTI_THREADED but for now its not supported.. If you are using long transactions without commit MVCC will be preferable, if not then MULTI_THREADED would be better I think.
-- 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=en.
