Hello, our application code did contain programming errors that prevented committing of some Hibernate transactions and the closing of Hibernate sessions. With H2 Version 1.4.191 (MV_STORE=FALSE) this caused a rapid growth in database file size. We did not see this growth issue using H2 Version 1.3.164.
Using the SCRIPT and RUNSCRIPT commands we can bring the DB size back to normal. Is there another way to tell H2 to throw away the garbage of the transactions that have not been closed? Reinhold -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
