We use H2 in a system where many (typically several hundreds) separate database are created. When users create new "projects" a copy is made of some self-contained template that also contains an initial database. We have converted the templates to have MVStore databases to phase out the use of PageStore ones. But the existing projects sometimes run for months or even up to several years and therefore we will be stuck with PageStore databases for quite some time.
Until version 1.9.196 (we skipped 1.4.197) we used MVCC on the PageStore databases. Although this was said to contain bugs we tested our applications very thoroughly and H2 as been very stable so far. However, the latest version (1.4.198) disables MVCC on PageStore databases altogether. Since moving to that version we have seen very much increased performance on MVStore databases but the PageStore databases have become noticeably slower than before. Converting all databases is almost impossible to achieve for us. Is there any way we could get H2 to do the same MVCC access on our PageStore databases as 1.4.196 did? Or has that functionality actually been ripped out? We use the same connection string and let H2 figure out the type of database but using distinct connection strings would be feasible. Silvio -- 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.
