Hi, > If it is simpler, are there are drawbacks to the new MVStore?
Yes. Traditionally, the problem of log structured storage is reclaiming disk space (or fast re-use of free space). This is specially a problem for file systems, if disk space usage is high (low free disk space). There are some smart (and complicated) algorithms to solve this problem. For H2 I plan to implement only a simple reclaim algorithm right now, and instead accept the fact that disk space usage is temporarily higher. For a database there are many cases where a log structured storage can actually save disk space, for example because there is no free space needed in b-tree pages (as there are no in-place updates); data can be more easily compressed, and there is no real need for a transaction log. A fully compressed database can actually be smaller with a log structured storage, but if you have many writes then it will probably need a bit more disk space; maybe 50% more or so. Regards, Thomas -- 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.
