Hi, The operations on RegularTable should be protected with the table level locking mechanism, and each b-tree belongs to exactly one table. So in theory it should work. But I understand there might be some bugs. My priority is to get the MVStore ready, and then make multi-threading work.
Regards, Thomas On Thu, Jan 2, 2014 at 9:39 AM, Uli <[email protected]> wrote: > Hi Noel, > > what a pity! Thanks for digging into the synching problems! > > It sounds to me as if MULTI_THREADED=1 should never be used and its usage > is strongly inadvisable. Can you add some strong warnings to the > documentation so that other users do not fall into the same trap? > > Thanks! > Uli > > >> Unfortunately, it proves to me that our MULTI_THREADED=1 support is not >> at all safe. >> >> For example, in the stacktrace below: >> >> ... >> >> >> The layers up to org.h2.command.CommandContainer are synchronized around >> the Session object. >> And the layers from org.h2.store.PageStore down are synchronized around >> the PageStore object. >> >> But the layers in between have no synchronization, but they are shared >> between multiple sessions. >> >> I am afraid I have no idea how to fix this, and it looks like quite a big >> job. >> >> >> -- > 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/groups/opt_out. > -- 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/groups/opt_out.
