Hi, > 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.
No, all bugfixes are listed in the change log. Could you provide some more information about your use case? I would like to know the settings, the table definitions (SCRIPT NODATA would list that). How many concurrent connection to the same database do you have, and what is the access pattern? > 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. That's OK. The socket locking should work, however I think the default file locking should also work - if it doesn't I would be interested to understand why. 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 -~----------~----~----~----~------~----~------~--~---
