Thanks for the valuable info you provided. I have no /CLOB/ nor /TEXT/ columns. These are the column types actually in use: /BOOLEAN, INT, DOUBLE, CHAR, VARCHAR, LONGVARCHAR, TIMESTAMP/.
I confirm the db size keeps growing even using the original H2 driver... so I still have to figure out a way to produce a standalone reproducible test case without sharing and adapting the entire legacy library. As further details, I've noticed that the legacy library uses a proprietary /DataSource/ for connection pooling that at jvm shutdown calls /Connection.close()/ on the pooled connections. This in turn calls to /LobStorage.removeAllForTable()/. I don't know how times it gets called. I simply see that if I take a thread dump in this phase, it is working on that calls. At the end the DB size slightly decrease. So i.e. * when a start the JVM with an empty DB and launch a import I get a DB size of less than 6gb * after the second import (where every import drops all objects as a first step) the DB size goes to 7667mb * after the JVM shutdown, the db size decreases from 7667mb to 7444mb (but it remains still much more than 6gb). Follows a partial call stack for a /Connection.close()/ call. I took it at JVM shutdown time for the Tomcat main thread on a JRockit JVM : H2 version is 1.3.169. Cheers Davide Noel Grandin wrote > On Fri, Aug 9, 2013 at 6:42 PM, davide.cavestro > < > davide.cavestro@ > > wrote: >> I actually don't use LOBs (could they be internally used by H2 in order >> to >> save the transaction log?) > > No, the LOB machinery is pretty only used for LOB's. Note that this > includes CLOB and TEXT columns, so maybe you have some of those? > > >> BTW I think having a way to access the list of pending transactions would >> be >> a valuable enhancement (it could be something like a readonly view with a > > Yeah, I've tried to implement this before. > Unfortunately, the problem is that H2 normally runs using a single > global lock for all it's data, so the query that wants to display the > metadata is blocked by the query currently executing. > Maybe when we switch to using MVStore as a our default engine, and > also make MULTI_THREADED=TRUE our default, it will become more > feasible. > > -- > 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+unsubscribe@ > . > To post to this group, send email to > h2-database@ > . > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/groups/opt_out. -- View this message in context: http://h2-database.66688.n3.nabble.com/h2-Continuous-Increase-in-H2-db-size-after-dropping-and-loading-same-data-repeatedly-tp4026836p4027113.html Sent from the H2 Database mailing list archive at Nabble.com. -- 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.
