The MVCC row level locking seemed like a big enough change which could change the dynamics of our application enough that we weren't ready to switch, although I'll be starting testing using it shortly. Were there other MVCC bug fixes in or since that release as well? I didn't see them in the release notes.
Regarding FILE_LOCK=SOCKET: each of our VMs has up to 30 active H2 databases, so we didn't want 30 extra threads per VM reading files every 5 seconds. I seem to recall we switched to socket locking from file locking due to some sort of slowdown, maybe a block waiting for a file lock on database startup? Don't quite remember, unfortunately. Thanks, Chris On Jan 10, 2009, at 6:01 AM, Thomas Mueller wrote: > > Hi, > >> I'm using H2 1.0.77 > > There were some changes in the MVCC code in version 1.0.79. Did you > try using this or a newer version? > >> FILE_LOCK=SOCKET > > Is this important for you? I don't think it is related to the problem, > but I like to understand why you need it. > > Regards, > Thomas > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
